-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi!
I had the same or at least a similar problem last night while
upgrading from lenny to squeeze.
I've made an apt-get upgrade with squeeze sources in my sources.list,
then upgraded my kernel as well as udev before actually rebooting and
then the
On Jan 16, Norbert Fischer no...@nerdpol.org wrote:
This may be very suboptimal if you are upgrading a remote server and
there's no way to reboot in an rescue system like i did afterwards.
Agreed, but there is no way I can debug and test this with enough
confidence without access to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately the Netra I was using is in a bad state, the LOM port
broke so, when it fails to start, I have to remove the drive, connect it
to a different server and edit the configuration.
I have another Netra somewhere but I didn't have the time
On Apr 18, Marco d'Itri m...@linux.it wrote:
for /dev/hdc too).
This one may be caused by the old IDE driver, you should try switching
your kernel to the new PATA driver.
Are there any news?
Anything?
--
ciao,
Marco
signature.asc
Description: Digital signature
On Mar 19, Marco d'Itri m...@linux.it wrote:
for /dev/hdc too).
This one may be caused by the old IDE driver, you should try switching
your kernel to the new PATA driver.
Are there any news?
--
ciao,
Marco
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco,
Sorry for not replying sooner, unfortunately the the LOM port of the
Netra T1 broke (RX works, TX doesn't), so it's very hard to test
different configurations. If the machine doesn't initialize the network
the only option I have is to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco,
Thanks for the hint.
As I said, deleting 70-persistent-net.rules solves the network problem
but every time I reboot the server
/etc/udev/rules.d/70-persistent-net.rules is recreated and at the next
reboot the network interfaces don't work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco,
Thanks for the hint.
As I said, deleting 70-persistent-net.rules solves the network problem
but every time I reboot the server
/etc/udev/rules.d/70-persistent-net.rules is recreated and at the next
reboot the network interfaces don't work
On Mar 19, Paolo Scarabelli pa...@msw.it wrote:
As I said, deleting 70-persistent-net.rules solves the network problem
but every time I reboot the server
/etc/udev/rules.d/70-persistent-net.rules is recreated and at the next
reboot the network interfaces don't work anymore.
I tought this was
Package: udev
Version: 151-2
Severity: normal
After upgrading from Lenny to Squeeze, cdrom and network adapters stopped
working.
Deleting both 70-persistent-cd.rules and 70-persistent-net.rules
from /etc/udev/rules.d and rebooting solved the problem.
70-persistent-net.rules has been recreated
On Mar 07, Paolo Scarabelli pa...@msw.it wrote:
After upgrading from Lenny to Squeeze, cdrom and network adapters stopped
working.
This is Sun-specific, which have multiple interfaces with the same IP
address. The underlying issue was fixed long ago and now working rules
are generated, I do not
11 matches
Mail list logo
