Bug 327609

Summary:	ipw3945 does not work
Product:	[openSUSE] openSUSE 10.3	Reporter:	DERUMAUX Marc <marc.derumaux>
Component:	Network	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	RC 1
Target Milestone:	---
Hardware:	64bit
OS:	openSUSE 10.3
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description DERUMAUX Marc 2007-09-23 21:37:45 UTC

I've been intalling Suse 10.3 for testing on my dell xps M1210.

Wifi :

My wifi card (intel pro wirless - 3945ABG) work on 10.2 with almost no problem.

It hasn't been configured on 10.3 install (packages ipw automatically installed but does not work at install and so not configured).

I could configure it by yast at first boot and it worked. After reboot, it doesn't work any more, even after re-configure it...

At each yast open, the firewall is automatically configured to "no trafic", whatever had been selected before... I don't know if it is normal way...

Bluetooth :

Bluetooth never worked on 10.2. (Kbluetooth applet stop just after starting)

On 10.3, Kbluetooth seems to work well as it does not stop and recognize all around neighbours' phone connections. My only bluetooth device is a Kingstone mouse but it is not recognised... Actually, the mouse is listed with all the phones in Kbluemon but moving the mouse does not affect cursor on the screen...

I tried to configure bluetooth in Yast : in advanced configuration, I would have liked to activate HID as it is explained in help to be related with mouse and keyboard but it is the only missing daemon in the list !

Hope this can help.

Best regards,

Marc

Comment 1 DERUMAUX Marc 2007-09-24 09:28:28 UTC

I just add half part solution regarding bluetooth. Stephan could help me on
bug 256000 and my bluetooth mouse work perfectly !

The wifi problem isn't solved unfortunately.

Marc

Comment 2 Mark Gordon 2007-09-24 21:00:11 UTC

The recent kernel upgrade would have caused this problem.  Reopen if you didn't upgrade your kernel recently (i,e. if you're not running 2.6.22.5-29).

*** This bug has been marked as a duplicate of bug 327595 ***