[haiku-development] Re: RTL8101/8102 FreeBSD Driver
- From: "Adrian Panasiuk" <adek336@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 14 Sep 2008 19:03:50 +0200
As for dprintf: while debuggingsome other network driver I found out that
not all messages get written to /var/log/syslog after being emitted with
dprintf; I know that they're emitted because replacing the dprintf s with a
null pointer dereference makes the kernel panic.
On Sun, Sep 14, 2008 at 6:20 PM, Michael Lotz <mmlr@xxxxxxxx> wrote:
> Hi Graham
>
> > Thanks for that Michael. I tried the line above, and while it now
> > doesn't crash, and seems to be able to send and receive packets
> > (ifconfig reports a small number sent and received) and while it also
>
> Nice to hear, that looks promising at least.
>
> > shows up in the Network Prefs, I can't get ping to work. If I try to
> > ping the ip of another machine on my lan (or google.com for that
> > matter), ping gets a return value of -1 and states:
> > ping: sendto: No route to host.
>
> I take it you set the connection up manually right now? Using ifconfig
> directly? The thing is, that (at least from my experience) Haiku is a
> bit fragile when it comes to manual configuration right now.
>
> The "no route to host" probably means that there is no route configured
> on which to reach your network addresses and no default route either.
> You can check that using the "route" command, where it probably doesn't
> list anything matching your network subnet. You could try adding a
> route manually (again using the "route" command) that "connects" the
> interface with the target network. Using "route --help" you should get
> an example of how it should work, something like "route add /dev/net/<
> drivername>/<devicenumber> default gw <gateway/router ip>" should work,
> as then all traffic should be routed through that gateway (you should
> get a 0.0.0.0 mapping when running "route" again).
>
> If that doesn't work, the safest bet is to just use automatic
> configuration. Others would know where exactly the network config is
> stored, so that you can just remove it to start over. You could just
> try a clean image with your driver added to check if automatic config
> works.
>
> If it also doesn't work with that, it's of course still possible that
> the driver doesn't really work at all. You could then add some
> dprintf's to the driver code and check that the output ends up in your
> /var/log/syslog. But I would really first try with the above.
>
> Regards
> Michael
>
>
--
Czy ty orzeł, czy ty kawka? -wkrótce zdłabi kaszel, czkawka.
Śmierć szyję zaszyje.
Other related posts:
