[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#548369: eth0: ERROR while getting interface flags: No such device



Frans,
I changed '#!/bin/sh' to '#!/bin/bash' in /sbin/hwup and /sbin/hwdown on the backup disk of the squeeze ugrade and booted from it. It fixes the issue. I did not change the default shell from bash to dash during the upgrade.

Thanks,
rlh 

-----Original Message-----
From: Frans Pop [mailto:elendil@planet.nl] 
Sent: Friday, September 25, 2009 4:16 PM
To: Hodge, Robert L; 548369@bugs.debian.org
Cc: Bastian Blank
Subject: Re: Bug#548369: eth0: ERROR while getting interface flags: No such device

reassign 548369 upgrade-reports
thanks

Please keep me in CC when replying!

On Friday 25 September 2009, Hodge, Robert L wrote:
> Description: eth0: ERROR while getting interface flags: No such device
>  Upgraded lenny on s390 to squeeze on s390, and upon rebooted received
>  the following messages.
>
> Setting up networking....
> Configuring network interfaces...
> SIOCSIFADDR: No such device
> eth0: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> SIOCSIFBRDADDR: No such device
> eth0: ERROR while getting interface flags: No such device
> eth0: ERROR while getting interface flags: No such device
> Failed to bring up eth0.
>
>  A backup was made of the squeeze install, and lenny was restored to the
> disk.

I'm reassigning this report to upgrade-reports for now as this is certainly 
not an installation issue.

First thing that needs to be done here is to find out the actual issue.
Possible candidates are the kernel, udev or sysconfig-hardware. I suspect 
the last.

Robert: please see the following bug report [1] and check if changing
'#!/bin/sh' to '#!/bin/bash' in /sbin/hwup and /sbin/hwdown fixes the 
issue. You'll probably have to reboot after making the change for it to 
take effect.
Did you change the default shell from bash to dash during the upgrade?

Bastian: any chance of an upload of sysconfig-hardware to fix this? I 
reported the issue 2 months ago...

Cheers,
FJP

[1] http://bugs.debian.org/538354

(Thanks to tbm for bouncing the BR to me.)





Reply to: