Debian 6 - qdio Device

[Riedel, Alexander]

Hi,

I have upgraded my Debian 5 to Debian 6 but after that my network-devices
Are not started automatically. I have to load manually the driver qeth_l2 and qeth
And also to group the devices and set it online before i can take the interface up.

What do i have to change to get this automatically as before ?

Thanks

Alexander

[Philipp Kern]

Post by Riedel, Alexander
I have upgraded my Debian 5 to Debian 6 but after that my network-devices
Are not started automatically. I have to load manually the driver qeth_l2 and qeth
And also to group the devices and set it online before i can take the interface up.
What do i have to change to get this automatically as before ?

What does `ls -R /etc/sysconfig' show?

Kind regards
Philipp Kern

[Stephen Powell]

Post by Riedel, Alexander
I have upgraded my Debian 5 to Debian 6 but after that my network-devices
Are not started automatically. I have to load manually the driver qeth_l2 and qeth
And also to group the devices and set it online before i can take the interface up.
What do i have to change to get this automatically as before ?

Hello, Alexander. I had the same problem. See

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612707

for a description of how I solved it. Reviewing outstanding bugs against the
"upgrade-reports" pseudo-package is a good idea when you are having upgrade
problems. Sometimes, someone else has had the same problem already.
--
.''`. Stephen Powell
: :' :
`. `'`
`-

[Riedel, Alexander]

Post by Riedel, Alexander
I have upgraded my Debian 5 to Debian 6 but after that my
network-devices Are not started automatically. I have to load manually
the driver qeth_l2 and qeth And also to group the devices and set it online before i can take the interface up.
What do i have to change to get this automatically as before ?

What does `ls -R /etc/sysconfig' show?

The output is listed here:
(The Dev 1000 is my dasd and 2000 is my OSA)


debian:/etc# ls -R /etc/sysconfig
ls -R /etc/sysconfig
/etc/sysconfig:
hardware scripts

/etc/sysconfig/hardware:
config-ccw-0.0.1000 config-ccw-0.0.2000

/etc/sysconfig/scripts:
common hardware

/etc/sysconfig/scripts/common:
functions

/etc/sysconfig/scripts/hardware:
functions hwdown-ccw-dasd hwup hwup-ccw-group
hwdown hwdown-ccw-group hwup-ccw hwup-ccw-zfcp
hwdown-ccw hwdown-ccw-zfcp hwup-ccw-dasd udev-net
debian:/etc#

[Philipp Kern]

I the meantime i have found the cause for the problem.
In /etc/udev/rules.d are old rules from Debian 5.
I have deleted now this rules and everything is working fine.

Well, when I looked at it some days ago it left me wondering why they're in
/etc in the first place. After all they override files in /lib/udev/rules.d
with the same content. Shouldn't people rather copy them to /etc to modify
them and then live with the consequences instead of having trouble on upgrades?

Kind regards
Philipp Kern

[Stephen Powell]

Post by Philipp Kern

I the meantime i have found the cause for the problem.
In /etc/udev/rules.d are old rules from Debian 5.
I have deleted now this rules and everything is working fine.

Well, when I looked at it some days ago it left me wondering why they're in
/etc in the first place. After all they override files in /lib/udev/rules.d
with the same content. Shouldn't people rather copy them to /etc to modify
them and then live with the consequences instead of having trouble on upgrades?

I'm no udev expert; but in the general case, I believe that the files in
/lib/udev/rules.d are intended to be templates used to generate the
files in /etc/udev/rules.d. The files in /etc/udev/rules.d tend to
be tailored to the user's environment in some way. For example, the
MAC addresses of the network adapters being used are typically present
in the versions in /etc/udev/rules.d. s390 is a special case in that, when the
OSA is in layer 3 mode, as mine is, there are no MAC addresses in the
files. In many cases, erasing one of the files in /etc/udev/rules.d
will cause a new one to be generated at the next boot up, but it may
or may not be what the user wants. This is particularly the case when
the system has more than one network adapter.
--
.''`. Stephen Powell
: :' :
`. `'`
`-

[Riedel, Alexander]

Hi,

I the meantime i have found the cause for the problem.

In /etc/udev/rules.d are old rules from Debian 5.
I have deleted now this rules and everything is working fine.

Alexander