[openbeosnetteam] Re: Build test???

> OK, lots of good info here.

Excellent.

>
> First.  I did get serial and syslog kernel debugging enabled, so that's
cool.
>  If I remember, I will put together a little "how to" this weekend for
> anybody that wants/needs to know that.
>
> Second.  Everything compiles and installs fine.  However, it appears that
> "make removedriver" doesn't remove net_stack_driver from
> /boot/home/config/add-ons/kernel/drivers/bin, so you have to manually
remove
> it to go back to the netserver stack (at least I did).  It seems to me
that
> it used to do that.

Aha, well that needs fixed then.

>
> Third.  Here's the "insane" debug from finding my net card and loading the
> stack.  Everything looks good to me.
>
> KERN 'rescan'[249]: publish_command(net_stack_driver): start
> KERN 'rescan'[249]: not known
> KERN 'rescan'[249]: net_stack_driver: init_hardware done.
> KERN 'rescan'[249]: net_stack_driver: init_driver, built May 16 2002
18:34:45
> KERN 'rescan'[249]: net_stack_driver: init_driver: core = 0x6043f4a0
> KERN 'rescan'[249]: module: network/protocol/icmp
> KERN 'rescan'[249]: module: network/protocol/ipv4
> KERN 'rescan'[249]: module: network/protocol/raw
> KERN 'rescan'[249]: module: network/protocol/route
> KERN 'rescan'[249]: module: network/protocol/tcp
> KERN 'rescan'[249]: module: network/protocol/udp
> KERN 'rescan'[249]:     UDP Module provided by network/protocol/udp
> KERN 'rescan'[249]:     TCP Module provided by network/protocol/tcp
> KERN 'rescan'[249]:     Raw IP module provided by network/protocol/raw
> KERN 'rescan'[249]:     IPv4 provided by network/protocol/ipv4
> KERN 'rescan'[249]:     ICMP (v4) provided by network/protocol/icmp
> KERN 'rescan'[249]:     Routing Sockets provided by network/protocol/route
> KERN 'rescan'[249]: module: network/interface/ethernet
> KERN 'rescan'[249]: 3c9xx(B) Be99H-WOL 2/24/99
> KERN 'rescan'[249]: Found 3Com Vortex/Boomerang cards found.2147454969
> KERN 'rescan'[249]: generic: no hardware found
> KERN 'rescan'[249]: <6>eepro100.c v1:v1
> KERN 'rescan'[249]: generic: no hardware found
> KERN 'rescan'[249]: etherpci: init_driver KERN 'rescan'[249]: init_driver:
> etherp
> ci not found
> KERN 'rescan'[249]: BeOS PCMCIA Card Services 3.0.14
> KERN 'rescan'[249]:   options:  [pci] [cardbus]
> KERN 'rescan'[249]: Intel PCIC probe: KERN 'rescan'[249]: not found.
> KERN 'rescan'[249]: homelan get_pci_list 0 entries
> KERN 'rescan'[249]: init_driver: homelan not found
> KERN 'rescan'[249]: init_driver: rtl8139 not found
> KERN 'rescan'[249]: tcm509 not found
> KERN 'rescan'[249]: BeOS PCMCIA Card Services 3.0.14
> KERN 'rescan'[249]:   options:  [pci] [cardbus]
> KERN 'rescan'[249]: Intel PCIC probe: KERN 'rescan'[249]: not found.
> KERN 'rescan'[249]: pc_init_card failed ffffffff
> KERN 'rescan'[249]: TLan:  init_driver()
> KERN 'rescan'[249]: TLan: TLan not found
> KERN 'rescan'[249]: tulip: init_driver KERN 'rescan'[249]: tulip LiteOn
found
> at
> IRQ b KERN 'rescan'[249]: tulip: publish_devices()
> KERN 'rescan'[249]: init_driver: vt86c100 not found
> KERN 'rescan'[249]: tulip: init_driver KERN 'rescan'[249]: tulip LiteOn
found
> at
> IRQ b KERN 'rescan'[249]: find_mii: Found phy= 1, control 3100 status 7829
> ID_1 0
> 302 ID_2 d008 autoN 01e1 linkP 05e1.
> KERN 'rescan'[249]: LiteOn found: irq 11 ioaddr 20049f00 ethernet address
> KERN 'r
> escan'[249]: 00:a0:cc:20:97:a3
> KERN 'rescan'[249]: tulip/0: IF_GETFRAMESIZE not supported, defaulting to
1500
> KERN 'rescan'[249]: module: network/interface/loop
> KERN 'rescan'[249]: net_stack_driver: uninit_driver
>
>
> Forth.  I put an address on the NIC, verified it with ifconfig and then
added
> a default route.  Ping doesn't work for me.  It just sites there and never
> responds.  Below is the output that I get.  That "KERN 'ping'" just
repeats
> over and over, so it almost appears like it's pinging, but can't answer a
> response.  Interestingly enough, I can ping from another machine to my
OBOS
> machine while this is going on and it works, so that's odd.

That's exactly what I had as well :) Something is brokne there for sure.

>
> KERN 'ping'[311]: net_stack_driver: init_driver, built May 16 2002
18:34:45
> KERN 'ping'[311]: net_stack_driver: init_driver: core = 0x6043f4a0
> KERN 'ping'[311]: net_stack_driver: net_stack_open(net/stack, O_RDWR)
return
> this
>  cookie: 0x02c9a3d8
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230200,
> 0xf
> d001a38, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe23020a,
> 0xf
> d001a34, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe23020b,
> 0xf
> d001a34, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230204,
> 0xf
> d001988, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230202,
> 0xf
> d001a04, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230204,
> 0xf
> d001680, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230202,
> 0xf
> d001a04, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230204,
> 0xf
> d001680, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230202,
> 0xf
> d001a04, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_control(0x02c9a3d8,
0xbe230204,
> 0xf
> d001680, 0)
> KERN 'ping'[311]: net_stack_driver: net_stack_close(0x02c9a3d8)
> KERN 'ping'[311]: net_stack_driver: net_stack_free(0x02c9a3d8)
> KERN 'ping'[311]: net_stack_driver: uninit_driver
>
>
> It would be nice if someone else could confirm that all of this checks out
> with what they see, rather than taking my word for it.  :-)

No, this all seems good. Your kernel hacking skills are getting better by
the day :)

Thanks for your efforts!

david

Other related posts: