Bug 148675 - Values filled in for Wireless USB device arn't used when device is plugged
Summary: Values filled in for Wireless USB device arn't used when device is plugged
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 SuSE Linux 10.0
: P5 - None : Minor
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-07 12:58 UTC by Jacques Weewer
Modified: 2008-06-25 09:53 UTC (History)
0 users

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


Attachments
Yast Directory with Logs (492.50 KB, application/x-bzip2)
2006-02-09 08:53 UTC, Jacques Weewer
Details
network files (43.60 KB, application/x-bzip2)
2006-02-09 13:07 UTC, Jacques Weewer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jacques Weewer 2006-02-07 12:58:02 UTC
I filled in all the values for my ZD1201 wireless USB chipset and they are saved via YaST. When plugging the device it doesn't use the settings that are filled in.  I gave it a fixed IP address and set it in ad-hoc more with no encryption. When it plug the device in it is being set in a managed mode with no IP address.
Comment 1 Jacques Weewer 2006-02-07 12:59:06 UTC
It looks like the filled in values arn't used from the /etc/sysconfig/network directory
Comment 2 Michael Gross 2006-02-07 13:34:37 UTC
Please attach the YaST logfiles as well as the resulting network configuration files from /etc/sysconfig. Also give more information about the used device using `hwinfo --...'.
Comment 3 Jacques Weewer 2006-02-07 18:52:34 UTC
information from hwinfo:
-----
50: USB 00.0: 0282 WLAN controller
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_ace_1201_noserial_if0
  Unique ID: rg_L.neImmHP29d6
  Parent ID: zPk0.vvGF92RIPJD
  SysFS ID: /devices/pci0000:00/0000:00:1d.3/usb4/4-2/4-2:1.0
  SysFS BusID: 4-2:1.0
  Hardware Class: network
  Model: "USB WLAN"
  Hotplug: USB
  Vendor: usb 0x0ace
  Device: usb 0x1201 "USB WLAN"
  Revision: "1.01"
  Driver: "zd1201"
  Features: WLAN
  Speed: 12 Mbps
  Module Alias: "usb:v0ACEp1201d0101dcFFdscFFdpFFicFFisc00ip00"
  Driver Info #0:
    Driver Status: zd1201 is active
    Driver Activation Cmd: "modprobe zd1201"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #49 (Hub)
-----

---
cat ifcfg-wlan-bus-usb-4-2\:1.0
BOOTPROTO='static'
BROADCAST=''
IPADDR='10.0.0.16'
MTU=''
NAME='USB WLAN'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='hotplug'
UNIQUE='rg_L.neImmHP29d6'
USERCONTROL='yes'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_ESSID='combine'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Ad-hoc'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='no'
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='bus-usb-4-2:1.0'
----
 and here is the iwconfig wlan0 output:
wlan0     IEEE 802.11b  ESSID:""  Nickname:"zd1201"
          Mode:Managed  Channel:6  Access Point: 00:00:00:00:00:00
          Bit Rate:1 Mb/s
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


I don't know what kind of information you want from the yast logs. If I know what you want I'm glad to give it.
Comment 4 Michael Gross 2006-02-08 11:32:21 UTC
Always attach the whole directory /var/log/YaST2 as tarball. The required information might be spreaded throughout these files.
Comment 5 Jacques Weewer 2006-02-09 08:52:34 UTC
(In reply to comment #4)
> Always attach the whole directory /var/log/YaST2 as tarball. The required
> information might be spreaded throughout these files.
> 

The tarball is attached, one little note the language setting was set to Dutch, I hope this isn't a big problem.
Comment 6 Jacques Weewer 2006-02-09 08:53:52 UTC
Created attachment 67133 [details]
Yast Directory with Logs

Language setting was dutch
Comment 7 Michael Gross 2006-02-09 10:56:40 UTC
Jacques: Please also attach the files in /etc/sysconfig/network/, thanks.
Comment 8 Jacques Weewer 2006-02-09 13:07:28 UTC
Created attachment 67228 [details]
network files

The files from /etc/sysconfig/network
Comment 9 Martin Vidner 2006-08-28 11:52:34 UTC
Reassigning to the new maintainer of yast2-network.
Comment 10 Michal Zugec 2007-03-23 07:44:39 UTC
later
Comment 11 Stephan Kulow 2008-06-25 09:35:23 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 12 Stephan Kulow 2008-06-25 09:37:30 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 13 Stephan Kulow 2008-06-25 09:42:08 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 14 Stephan Kulow 2008-06-25 09:53:32 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(