Bug 112870 - at76c503a drivers are not yet able to be used
Summary: at76c503a drivers are not yet able to be used
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 2
Hardware: i586 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Joachim Gleissner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 23:05 UTC by Valentin Schäfer
Modified: 2005-11-07 15:10 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Schäfer 2005-08-24 23:05:15 UTC
my d-link dwl-120 (revision E1) w-lan usb adapter cannot be used under suse 
10.0 beta 1 and 2. i wanted to install it and he found it, but as i wanted to 
configure it in yast, he first said that he has to install a package 
called "atmel-firmware" and after that he told me that the package was not 
found on the medium. after that i downloaded the firmware rpms from the 
berlios server and wanted to install them but the same error came. after that 
i downloaded a gzip package and wanted to start the installer in the console, 
but he cancelled with an error. he said that the "hotplug-services" or 
something like that is missing. totally frustrated, i copied the firmware into 
the right directory and was after a reboot able to configure my w-lan adapter 
via "iwconfig" (but still no success with yast), but my card doesn't want to 
connect her into my w-lan network...
am i just stupid or is this a bug that has to be fixed??
greets from munich,
Valentin Schäfer
Comment 1 Joachim Gleissner 2005-08-25 08:46:38 UTC
Please attach /var/log/messages. The firmware packages or not included in  
openSUSE, you can download apropriate packages from  
ftp.suse.com:pub/suse/i386/10.0/....  
Comment 2 Joachim Gleissner 2005-11-07 15:10:05 UTC
No further information -> closing as INVALID. Please reopen in case the problem still exists.