Configuring network interfaces... No lease, forking to background

[Javi]

Hello,


I get this message when booting my BeagleBoard-xM:



Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such
device
udhcpc (v1.13.2)
started
Sending
discover...
Sending
discover...
Sending
discover...
No lease, forking to background

I don't know what is wrong, but the ethernet port doesn't work. I've
been looking around on the internet but I don't find any solution.

Maybe, you could point me to anything.

Thanks.

Javi

[Max Galemin]

Hi Javi,

Not enough information... Did you enable support for SMSC95XX in
network ethernet adapters in your kernel config? What kernel do you
use? For example in new kernel (2.6.36) you need to change next line
in "arch/arm/mach-omap2/board-omap3beagle.c" in function
"beagle_twl_gpio_setup":

gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0);

Change to:

gpio_direction_output(gpio + TWL4030_GPIO_MAX, 1);


Cheers,
Max.

[freddyglima]

Hello Javi,
the easiest way to solve your problem is to connect a monitor usind
DVI-D connector and you can set the correct IP configurations using
Linux interface.

The other way, would be to edit the IP settings using vi editor from
the terminal. The file to be edit is in /etc/network/interfaces.
After editing the file, you probably have to do stop the networking
and start it again:

/etc/init.d/networking stop
/etc/init.d/networking start

Both should work.
Regards,
Frederico

[Cedric Madianga]

Hi Javi,

By default, the network interface of the BeagleBoard xm is not
configured.

There are 3 things to do to enable it:

1/ You have to add the driver that supporting the LAN9514 device into
your kernel image.
So, set CONFIG_USB_NET_SMSC95XX=y in
Device drivers
-> Network Device Support
-> USB Network Adapters
-> Multi purpose USB Networking Framework
-> SMSC LAN95XX based USB 2.0 10/100 ethernet devices

2/ You have to detect and init the ethernet controller during boot
thanks to USB enumeration.
To do that, set CONFIG_USB_EHCI_HCD= y in
Device drivers
-> Network Device Support
-> EHCI HCD (USB 2.0) support

3/ You have to patch the arch/arm/mach-omap2/board-omap3beagle.c file
as below:
/* TWL4030_GPIO_MAX + 0 == ledA, EHCI nEN_USB_PWR (out, active low) */
gpio_request(gpio + TWL4030_GPIO_MAX, "nEN_USB_PWR");
gpio_direction_output(gpio + TWL4030_GPIO_MAX, 1);

Regards,

Cedric.

[Dale Weber]

On Monday, November 22, 2010 03:03:35 am freddyglima wrote:

> The other way, would be to edit the IP settings using vi editor from
> the terminal. The file to be edit is in /etc/network/interfaces.
> After editing the file, you probably have to do stop the networking
> and start it again:
>
> /etc/init.d/networking stop
> /etc/init.d/networking start

Just do /etc/init.d/networking restart

8-Dale
--
Open your mind, Read, Learn, Think, Apply, and Have Fun!
AllStarLink Node 2392 | EchoLink node 6185 | 73, from N7PKT!
Main site: http://www.hybotics.com | Blog: http://www.hybotics.info
Just because we can, does it follow that we should?

[Javi]

Thanks,

I am using the kernel 2.6.32. Maybe it is better to use a newer one,
the 2.6.36.

I am using the serial console, and it is enough for me for the moment.
I want to learn how to build an embedded linux system, so it will be
good to try to compile my own kernel, but I don´t know where I could
get the correct kernel. Could you point to me in any direction,
please?

Thanks a lot.

Javi.-

[Javi]

Thanks Max,

I am using the kernel 2.6.32 (it comes with the angstrom demo is
included with the BB-xM). Is it possible to enable support for
SMSC95xx with this kernel? If not, I guess I´ll have to try with the
new kernel as you say. Do you know how/where to get this one? These
are my first steps with embedded linux... sorry if the question is too
basic. I have been googling without success.

freddyglima

I haven´t got a monitor with DVI-D input, so I use the serial console,
and that is enough for me. I have tried changing the IP and stopping
and restarting the network, but it is not enough. I think that I will
need to make some modifications and recompile the kernel, if
necessary.

Thanks for your help

On 22 nov, 03:11, Max Galemin <maksim.gale...@gmail.com> wrote:

[Max Galemin]

Hi Javi,

Your kernel 2.6.32 is OK (it's a much better and much more stable than
2.6.36 as there is a lot of useful features in 2.6.32 which are not in
a mainline yet). I spent a lot of time stabilizing 2.6.36 and as a
result I decided to work with 2.6.32. :)

Definitely you can enable support for SMSC95xx in 2.6.32 - please see
comment form Cedric Madianga how to do this. But first of all check
that you don't have support for this chip in your kernel. If your
kernel has support for this chip you'll the next lines in your
kernel's boot traces (probably not 'eth0' but 'usb0' but it doesn't
matter):

Jan 1 01:07:06 calima user.info kernel: [ 4040.918853] eth0: register
'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet,
00:ff:ff:ff:ff:01
Jan 1 01:07:08 calima user.info kernel: [ 4043.250488] eth0: link up,
100Mbps, full-duplex, lpa 0x45E1


Cheers,
Max.

[Javi]

Hi,

I have these lines:

[ 44.020202] smsc95xx v1.0.4
[ 44.101226] usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1,
smsc95xx USB 2.0 Ethernet, de:f6:66:56:35:e7
[ 46.318847] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 46.325164] devtmpfs: mounted
[ 46.330688] Freeing init memory: 204K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
[ 48.745788] FAT: bogus number of reserved sectors
[ 48.753082] VFS: Can't find a valid FAT filesystem on dev mmcblk0.
[ 49.085937] FAT: bogus number of reserved sectors
[ 49.093322] VFS: Can't find a valid FAT filesystem on dev
mmcblk0p2.
Remounting root file system...
Caching udev devnodes
Populating dev cache

Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such
device
udhcpc (v1.13.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background

Cheers,

Javi