Mailinglist Archive: opensuse-mobile (18 mails)
| < Previous | Next > |
Re: [opensuse-mobile] Help Need with Dell Inspiron E1705 and wireless set-up
- From: "G.T.Smith" <grahamsmith@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Mar 2007 10:25:37 +0100
- Message-id: <4608E311.1050608@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Ralph De Witt wrote:
> On Wednesday 21 March 2007 15:03, K. Elo wrote:
>
>> Hi Ralph,
>>
>> Ralph De Witt wrote (21.3.2007 16:50):
>>
>>> Hello All:
>>> I just purchased a Dell Inspiron E1705 with a wireless minicard that
>>> has a Broadcomm 4311 chip. I am new to opensuse and seem unable to
>>> get wireless going. So far I have found no advice that works. Can
>>> someone help me out. Thanks a million.
>>>
>> Either read:
>> - http://forums.suselinuxsupport.de/index.php?showtopic=41983
>>
>> Or try the following steps (worked for me with my AcerAspire 3020 with
>> BCM43xx-based WLAN just fine):
>>
>> 1) Install (with YaST) following packages:
>> - bcm43x-fwcutter
>> - wlan-kmp-default
>> - kdenetwork3-wireless
>> - wireless-tools
>>
>> 2) Install firewire (by entering in console as root):
>> 'install_bcm43xx_firmware' (without quotes!)
>>
>> 3) Now Your computer should fetch the newest firmware for Broadcom.
>>
>> 3) When finished, start Yast->Network Devices->Network card
>> - Select "User controlled with NetworkManager"
>> - You should now see Your WLAN-controller as "unconfigured decive"
>>
>> 4) Configure ("Edit") the card. Remember to check that the controller
>> uses the module "bcm43xx " (Edit, on the Address-Tab, select
>> Advanced->Hardware Details).
>> - Please note: the card will be configured as eth#, not as wlan#
>> (#=0,1,...).
>>
>> 5) Finish the configuration of Network cards and close Yast.
>>
>> 5) Start KNetworkManager and activate wireless
>>
>> 6) When You now click on the KNetworkManager icon on the dock panel, You
>> should see all wireless networks available in your neighbourhood. Just
>> select the right one with a mouse click and wait until the connection
>> is established.
>>
>> Hope this helps!
>> Kimmo
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: opensuse-mobile+unsubscribe@xxxxxxxxxxxx
>> For additional commands, e-mail: opensuse-mobile+help@xxxxxxxxxxxx
>>
> To all:
> I have tried all the procedures listed but my wireless card is still not seen.
> Even tried ndiswrapper and still no go. I am at a dead end now. Thanks for
> all your help so far.
>
Not worked with particular hardware but it should be noted that with
SuSE 10.2 the WiFi is loaded via udev so much earlier documentation on
how to setup WiFi does not scan. Personally, I would go nowhere near
KNetworkManager. I found it somewhat unreliable and Klunky. If for some
reason the WiFi hardware device driver has not correctly loaded the if*
utilities are useless so you need to ensure the hardware drivers are
loaded first.
If YaST is not detecting the card and it is not seen with hwinfo (lspci
lists pci devices so may not detect stuff on usb or firewire) then
either there is something missing i.e. support for the bus the minicard
is not installed or there is no support for this type of device. If it
is seen in hwinfo but not by YaST this probably means the driver is
unavailable to YaST. This will mean that you need acquire the card
driver and either load it via modprobe and manually edit/create a
configuration file in /etc/sysconfig/network. or manually configure the
device in Yast and set the WLAN connection settings. In the latter case
the configuration file should be generated by YaST. Make sure the WiFi
support is loaded manually, WiFi on boot has given me more problems than
it solved in Linux, and it is definitely not a good idea to do this
until you have ensured that it works as expected.
This does not mean you are finished yet. If after this the device can be
seen via ifconfig and can be loaded with ifup you are ok. If not the
following script framework worked for me..... I currently sudo into
this... (I have the probably bad habit of using the /etc/init.d scripts
rather than rc* script form....) ifconfig will do this as well but
there does seem to a problem with udev on my machine that this script
handles and ifconfig does not.
#! /bin/bash
# a)
cp /etc/udev/rules.d/30-net_persistent_names.oldrule
/etc/udev/rules.d/30-net_persistent_names.rules
hwup wlan-id-00:0e:35:cd:e5:23 bus-pci-0000:02:0b.0
# b)
# Wait for wireless card to intialise
#
sleep 30
[local mount stuff deleted]
# c)
# Restart CUPS so network printers are detected
#
if /etc/init.d/cups restart
then
echo CUPS reset
else
echo CUPS reset fail
fi
#
# Restart CUPS nice reset
#
if /etc/init.d/cupsrenice restart
then
echo CUPS nice reset
else
echo CUPS nice reset fail
fi
Comments
a) The /etc/udev/rules.d folder contains the rules for udev, I override
the current rule file with an initial rule file to stop a problem I have
with incrementing network device assignments (others may not need to do
this). hwup initiates the WiFi hardware and assigns the network device
link, the wlan config file is found in /etc/sysconfig/network (as
ifcfg-<wlan config>). The second parameter will vary according to your
network configuration (use hwinfo to find this out) and it identifies
the bus the device is on, the file concerned are kept in
/etc/sysconfig/hardware.... If this works the device becomes available
to the if* tools and should already be loaded and connected.
b) Need to put in a delay as it can take a bit of time for the
connection to be negotiated.
c) if you are using CUPS to connect to a network printer restarting CUPS
is essential otherwise CUPS will not see it (it does not seem to want to
dynamically reconnect if a device becomes available). There probably is
a better way of doing this but I have not found it yet.
In the main I would not connect WiFi on boot at moment. I would try
something like the above sequence to see if you can get something going
manually first. Then I would see if works in the boot process.
BTW This is nothing to some of the grief I have had with XP, at least
SuSE linux once connected stays connected and handles connection hiccups
fairly smoothly.....
The following link gives details of WiFi kit that is supposed to work
open SuSE
> http://en.opensuse.org/HCL/Network_Adapters_%28Wireless%29
The link below is a bit more comprehensive
> http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/
begin:vcard
fn:Graham T. Smith
n:Smith;Graham T.
adr:Barton upon Humber;;90 Bowmandale;;North Lincs.;DN18 5EA;UK
email;internet:grahamsmith@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
tel;cell:07876793607
version:2.1
end:vcard
> On Wednesday 21 March 2007 15:03, K. Elo wrote:
>
>> Hi Ralph,
>>
>> Ralph De Witt wrote (21.3.2007 16:50):
>>
>>> Hello All:
>>> I just purchased a Dell Inspiron E1705 with a wireless minicard that
>>> has a Broadcomm 4311 chip. I am new to opensuse and seem unable to
>>> get wireless going. So far I have found no advice that works. Can
>>> someone help me out. Thanks a million.
>>>
>> Either read:
>> - http://forums.suselinuxsupport.de/index.php?showtopic=41983
>>
>> Or try the following steps (worked for me with my AcerAspire 3020 with
>> BCM43xx-based WLAN just fine):
>>
>> 1) Install (with YaST) following packages:
>> - bcm43x-fwcutter
>> - wlan-kmp-default
>> - kdenetwork3-wireless
>> - wireless-tools
>>
>> 2) Install firewire (by entering in console as root):
>> 'install_bcm43xx_firmware' (without quotes!)
>>
>> 3) Now Your computer should fetch the newest firmware for Broadcom.
>>
>> 3) When finished, start Yast->Network Devices->Network card
>> - Select "User controlled with NetworkManager"
>> - You should now see Your WLAN-controller as "unconfigured decive"
>>
>> 4) Configure ("Edit") the card. Remember to check that the controller
>> uses the module "bcm43xx " (Edit, on the Address-Tab, select
>> Advanced->Hardware Details).
>> - Please note: the card will be configured as eth#, not as wlan#
>> (#=0,1,...).
>>
>> 5) Finish the configuration of Network cards and close Yast.
>>
>> 5) Start KNetworkManager and activate wireless
>>
>> 6) When You now click on the KNetworkManager icon on the dock panel, You
>> should see all wireless networks available in your neighbourhood. Just
>> select the right one with a mouse click and wait until the connection
>> is established.
>>
>> Hope this helps!
>> Kimmo
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: opensuse-mobile+unsubscribe@xxxxxxxxxxxx
>> For additional commands, e-mail: opensuse-mobile+help@xxxxxxxxxxxx
>>
> To all:
> I have tried all the procedures listed but my wireless card is still not seen.
> Even tried ndiswrapper and still no go. I am at a dead end now. Thanks for
> all your help so far.
>
Not worked with particular hardware but it should be noted that with
SuSE 10.2 the WiFi is loaded via udev so much earlier documentation on
how to setup WiFi does not scan. Personally, I would go nowhere near
KNetworkManager. I found it somewhat unreliable and Klunky. If for some
reason the WiFi hardware device driver has not correctly loaded the if*
utilities are useless so you need to ensure the hardware drivers are
loaded first.
If YaST is not detecting the card and it is not seen with hwinfo (lspci
lists pci devices so may not detect stuff on usb or firewire) then
either there is something missing i.e. support for the bus the minicard
is not installed or there is no support for this type of device. If it
is seen in hwinfo but not by YaST this probably means the driver is
unavailable to YaST. This will mean that you need acquire the card
driver and either load it via modprobe and manually edit/create a
configuration file in /etc/sysconfig/network. or manually configure the
device in Yast and set the WLAN connection settings. In the latter case
the configuration file should be generated by YaST. Make sure the WiFi
support is loaded manually, WiFi on boot has given me more problems than
it solved in Linux, and it is definitely not a good idea to do this
until you have ensured that it works as expected.
This does not mean you are finished yet. If after this the device can be
seen via ifconfig and can be loaded with ifup you are ok. If not the
following script framework worked for me..... I currently sudo into
this... (I have the probably bad habit of using the /etc/init.d scripts
rather than rc* script form....) ifconfig will do this as well but
there does seem to a problem with udev on my machine that this script
handles and ifconfig does not.
#! /bin/bash
# a)
cp /etc/udev/rules.d/30-net_persistent_names.oldrule
/etc/udev/rules.d/30-net_persistent_names.rules
hwup wlan-id-00:0e:35:cd:e5:23 bus-pci-0000:02:0b.0
# b)
# Wait for wireless card to intialise
#
sleep 30
[local mount stuff deleted]
# c)
# Restart CUPS so network printers are detected
#
if /etc/init.d/cups restart
then
echo CUPS reset
else
echo CUPS reset fail
fi
#
# Restart CUPS nice reset
#
if /etc/init.d/cupsrenice restart
then
echo CUPS nice reset
else
echo CUPS nice reset fail
fi
Comments
a) The /etc/udev/rules.d folder contains the rules for udev, I override
the current rule file with an initial rule file to stop a problem I have
with incrementing network device assignments (others may not need to do
this). hwup initiates the WiFi hardware and assigns the network device
link, the wlan config file is found in /etc/sysconfig/network (as
ifcfg-<wlan config>). The second parameter will vary according to your
network configuration (use hwinfo to find this out) and it identifies
the bus the device is on, the file concerned are kept in
/etc/sysconfig/hardware.... If this works the device becomes available
to the if* tools and should already be loaded and connected.
b) Need to put in a delay as it can take a bit of time for the
connection to be negotiated.
c) if you are using CUPS to connect to a network printer restarting CUPS
is essential otherwise CUPS will not see it (it does not seem to want to
dynamically reconnect if a device becomes available). There probably is
a better way of doing this but I have not found it yet.
In the main I would not connect WiFi on boot at moment. I would try
something like the above sequence to see if you can get something going
manually first. Then I would see if works in the boot process.
BTW This is nothing to some of the grief I have had with XP, at least
SuSE linux once connected stays connected and handles connection hiccups
fairly smoothly.....
The following link gives details of WiFi kit that is supposed to work
open SuSE
> http://en.opensuse.org/HCL/Network_Adapters_%28Wireless%29
The link below is a bit more comprehensive
> http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/
begin:vcard
fn:Graham T. Smith
n:Smith;Graham T.
adr:Barton upon Humber;;90 Bowmandale;;North Lincs.;DN18 5EA;UK
email;internet:grahamsmith@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
tel;cell:07876793607
version:2.1
end:vcard
| < Previous | Next > |