|
Bugzilla – Full Text Bug Listing |
| Summary: | rt2400/rt2500 invalid device name. | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Ivo van Doorn <IvDoorn> |
| Component: | Network | Assignee: | Christian Zoz <zoz> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Ivo van Doorn
2005-09-04 12:29:15 UTC
I don't know why the devices are renamed. Christian? However, why shouldn't the network function with these names? Because Ralink was so 'kind' to hardcode the ra%d naming into the module. And the Ralink Utility is depending on this name to actually work. :( And since quite a bit of functionality of the driver is accessed through the private ioctls which require structures and other obscure formatted data, there are quite a few people who use the Utility. SuSE is one of the very few distros who have made sure their configuration Utility can handle the Ralink drivers, so people also use the Ralink Utility for easy configuration. So we cannot drop the Utility that easily. The rt2x00 module, which just entered the Beta stage does not have these constraints. I have just tested the device names after a fresh installation, the names are correctly setup to ra0/ra1/rausb0. > I have just tested the device names after a fresh installation, the names are
> correctly setup to ra0/ra1/rausb0.
Update from one beta to another can have special effects.
|