| To: | "Michael Renzmann" <mrenzmann@xxxxxx> |
|---|---|
| Subject: | Re: Fw: [Bugme-new] [Bug 3777] New: tun driver fails to open whenbuilt in, must be modular |
| From: | shemminger@xxxxxxxx |
| Date: | Fri, 19 Nov 2004 21:32:45 -0800 (PST) |
| Cc: | netdev@xxxxxxxxxxx |
| Importance: | Normal |
| In-reply-to: | <419ED5CB.3080106@web.de> |
| References: | <20041119150808.578154d3.akpm@osdl.org> <419ED5CB.3080106@web.de> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | SquirrelMail/1.4.2-1_osdl_00 |
> Hi. > > Andrew Morton wrote: >> Problem Description: kernel will not assign/open a tun device when tun.o >> is >> compiled as a built-in. ifconfig gives 'unable to open /dev/net/tun' >> error. >> compiling as a module fixes. > > If anyone can give me a small general hints for what might be the cause > of this problem, I could take a look at it. I already have some patches > for tun.o (that needs to be sent to the maintainer), another one doesn't > hurt :) But since I'm not yet too experienced with programming of kernel > modules, any help would be appreciated. > > Bye, Mike > See if it successfully registers with the misc driver (misc_register). I suspect it is an initialization order type thing. Probably the code to register with the misc driver (to create the device) should just be delayed until the network device is brought up (ie dev->open) is called. Good luck. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Fw: [Bugme-new] [Bug 3777] New: tun driver fails to open when built in, must be modular, Michael Renzmann |
|---|---|
| Next by Date: | Re: Assertions when lowering tcp_tso_win_divisor, David S. Miller |
| Previous by Thread: | Re: Fw: [Bugme-new] [Bug 3777] New: tun driver fails to open when built in, must be modular, Michael Renzmann |
| Next by Thread: | Re: r8169.c, Dorn Hetzel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |