Bug 145750 - HAL doesn't list info.capabilites for some (all?) PCMCIA network cards
Summary: HAL doesn't list info.capabilites for some (all?) PCMCIA network cards
Alias: None
Product: Fedora
Classification: Fedora
Component: hal   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-21 02:15 UTC by Rodd Clarkson
Modified: 2013-03-06 03:42 UTC (History)
2 users (show)

Fixed In Version: 0.4.7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-25 04:21:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output from 'lshal &> /tmp/lshal.output' (32.63 KB, text/plain)
2005-01-23 12:06 UTC, Rodd Clarkson
no flags Details

Description Rodd Clarkson 2005-01-21 02:15:13 UTC
Description of problem:

HAL doesn't list info.capabilites for my PCMCIA network cards (RT-2400
and RT-2500).  As a result, Network Manager is unaware of the
existence of these network devices.

As I understand it, HAL (using either hal-device-manager or pshal)
should show an entry something like

	info.cababilities	string	net.80211 net

for PCMCIA cards.  Unfortunately, HAL doesn't even show this 'field',
let alone that the card has network type capabilites.

Comment 1 David Zeuthen 2005-01-21 16:01:32 UTC

yeah, this stopped working when the sysfs patch for PCMCIA cards was
introduced somewhere in 2.6.10; it worked fine under 2.6.9. Please try
the new packages here


that should fix the problem.


Comment 2 Rodd Clarkson 2005-01-23 12:03:31 UTC
This didn't work for me.

Regarding you comment above that suggests this is a regression, this
has never worked for me.  This is not (AFAIK) a regression.  At no
time that I'm aware of has HAL reported these cards as having
info.capabilites.  Certainly not during the 2.6.9 kernels anyway.

I'm still not seeing any info.capabilities for this card.  I'll attach
the output from pshal so that you can see what I'm getting.

Comment 3 Rodd Clarkson 2005-01-23 12:06:01 UTC
Created attachment 110104 [details]
output from 'lshal &> /tmp/lshal.output'

Comment 4 Rodd Clarkson 2005-01-23 12:08:01 UTC
Oh, that should have been lshal, not pshal.

Also, the card(s) in questions show up in the section for pci.vendor =
'RaLink' (string) to make it easier to find.  As mentioned, it should
have a info.capabilities entry that says it's a wireless network card.

Comment 5 David Zeuthen 2005-01-23 15:05:53 UTC
It seems that your card is _Cardbus_ (e.g. the kernel sees it as just
another PCI device) and not a 16-bit PCMCIA card. Here's a short


So, it seems that you are simply missing the driver. Hence, this is
not a hal bug and it explains why it has never worked for you. It
seems there is a driver you can use here


but the usual disclaimers apply (e.g. if it breaks anything, you get
to keep both pieces).

Since I've tested this myself on a Cisco 16-bit PCMCIA card using the
airo driver, I'm going to close this bug when the fixed package is


Comment 6 Rodd Clarkson 2005-01-25 04:13:40 UTC
Okay.  I was using the driver us mention at the time of filing this
bug.  I've since upgraded to the current beta release of the new driver.

Neither driver sees the card being reported by HAL as having

If this is a driver issue, could you tell me what the driver is
supposed to be doing so that HAL will know what the device can do. 
Some site or something that I can point the driver developers to that
they could use as a reference.

Comment 7 Rodd Clarkson 2005-01-25 04:16:25 UTC
Reopening bug because the problem hasn't actually been resolved for me.

Comment 8 David Zeuthen 2005-01-25 04:21:42 UTC
Did I not make myself clear in comment 5? This is a _driver issue_,
not a hal issue, so it makes little sense to reopen this bug.

As to solving your problem, check that the directory


contains two symlinks called device and driver (replace eth0 with the
name of the device; /var/log/messages may be helpful here). If it
doesn't go bug the driver authors; it's pretty easy to fix (just a

Note You need to log in before you can comment on or make changes to this bug.