Bug 142759 - hwup doesn't work with S/390 network devices
Summary: hwup doesn't work with S/390 network devices
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Alpha 4
Hardware: S/390-64 Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Christian Zoz
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-12 08:17 UTC by Hannes Reinecke
Modified: 2007-06-05 09:37 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hannes Reinecke 2006-01-12 08:17:48 UTC 
After installation hwup is not able to configure the network device.
It fails with the message:

'hwup error: could not get driver name'

After closer inspection, hwup contains at least two errors:

- If no 'DRIVER' is set in hwcfg, it tries to look for the appropriate driver name. Unfortunately only on BUS_0; if the driver is on a bus chain (ie BUS_N > 1) it should rather look for the _last_ bus entry.
- bind/unbind support will fail horribly on s/390 as we're using more than one channel for a device; we need to unbind _all_ of them for this to work.
Rather: we don't need bind/unbind support as we can activate devices individually.
Comment 1 Christian Zoz 2006-01-31 19:15:17 UTC 
This one is fixed since two weeks.