Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 20 Oct 2014, 06:27
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking » Wireless
How to use Broadcom BCM5705M in retroprecise-543?
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [14 Posts]  
Author Message
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Tue 26 Nov 2013, 12:57    Post subject:  How to use Broadcom BCM5705M in retroprecise-543?  

I am installing retroprecise-5.4.3.
How to get Broadcom NetXtreme BCM5705M Gigabit Ethernet (rev 01) wireless working?
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 5231
Location: Charleston S.C. USA

PostPosted: Tue 26 Nov 2013, 13:01    Post subject:  

Try this:
Guide for setting up wireless connection:
http://www.murga-linux.com/puppy/viewtopic.php?t=65346

If it does not work.
You do what?
You see what?

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Tue 26 Nov 2013, 14:53    Post subject:  

Connect to Internet by Wired or wireless LAN
Internet Connection Wizard
OK

Puppy Network Wizard
interface Type Module Device Description
Eth1 Wireless ipw 2200 Intel 2200BG Calexico2 Network Connection

The PCI Devices - System information shows:

Intel Corporation PRO/Wireless 2200BG {Calexico2} Network Connection (rev 05)

Clicked on eth1

Configure network interface eth1 window opens:
Clicked on "Wireless" button

Puppy Network Wizard came up:
to create new profile clicked on "Scan" button

Select one of the available networks - Selected my router, 01:linksys

Select profile to load - autoconnect or template Selected autoconnect
clicked on "Load" button

Edit profile section shows Encryption to be WEP - I can't switch to open. I want open!

Went back to Select a profile to load Selected template.
Encryption now shows "Open"

Profile name shows template
ESSID shows hotspot

Mode comes up Managed, and Open

Saved

Configure network interface eth1 appears
clicked on "Test eth1" button.
testing eth1

REPORT ON TEST OF eth1 CONNECTION
unable to connect.

Verified wireless network is available from my other laptop using wireless.

~ $ ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=1.53 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=1.36 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=1.20 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=1.20 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=1.16 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.166/1.294/1.535/0.139 ms

Do I need to click on Windows button to install a windows driver? I would expect to do so if the wireless was Broadcom. If so where do I get it?
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Tue 26 Nov 2013, 19:37    Post subject:  

My Bad

my wireless device is:

Intel Corporation PRO/Wireless 2200BG {Calexico2} Network Connection (rev 05)

I was able to get wireless connection after rebooting. The problem now is that I do not stay connected. The connection lasts less than a minute.

I can right click on the network icon at the bottom right corner of the scree and disconnect. I can then right click on it again and reconnect. I will then get a connection that does not last very long.

connecting to DHCP server...timeout in 30 seconds

Sucess

I just pinged my router:
5 packets sent, 2 received, 60% packet loss

Disconnected and reconnected - network unreachable

hovering cursor over the icon I get; active interfaces: eth1

Disconnected and reconnected.

success

5 sent 3 received 2 lost.

ping again

5 sent no loss

ping again

5 sent 1lost

ping

5 sent 3 lost

ping

5 sent no loss

My other laptop which I am using right now is showing no packet loss, it stays connected continuously.
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Wed 27 Nov 2013, 11:13    Post subject:  

Check what you find with: modinfo ipw2200.

You should find from alias row something which contain 8086:4220 chip id.

PCI: 8086:4220 Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection

Something like this:
alias: pci:v00008086d00004220sv*sd*bc*sc*i*

If you dont find corresponding chip support, then the included ipw2200 does not support your chip.

If it finds the support for the chip, then the problem lies on somewhere else.

For example, are the needed firmwares included:
firmware: ipw2200-bss.fw
firmware: ipw2200-sniffer.fw
firmware: ipw2200-ibss.fw

/lib/modules/all-firmware/ipw2200_firmware-3.0

Hmm....the folder name suggests that the support might start from the kernel 3.0.

What kernel version is in Retro-Precise ?
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Wed 27 Nov 2013, 13:06    Post subject:  

Does not look like there is chip support.

3.2.29 kernel for 5.4.3 Precise Puppy

Precise Puppy retro is almost the same, except built with a non-PAE kernel. The differences are explained further in this readme.

No mention about the kernel at the readme:
http://distro.ibiblio.org/quirky/precise-5.4.3-retro/precise-5.4.3-retro-README.htm

Can I ID the kernel version from the command line?

What to do?

Results of modinfo ipw 2200:

# modinfo ipw2200
filename: /lib/modules/3.2.32/kernel/drivers/net/wireless/ipw2x00/ipw2200.ko
firmware: ipw2200-bss.fw
firmware: ipw2200-sniffer.fw
firmware: ipw2200-ibss.fw
license: GPL
author: Copyright(c) 2003-2006 Intel Corporation
version: 1.2.2kmq
description: Intel(R) PRO/Wireless 2200/2915 Network Driver
srcversion: CF2C4E4B2E079119B3F3726
alias: pci:v00008086d00004224sv*sd*bc*sc*i*
alias: pci:v00008086d00004223sv*sd*bc*sc*i*
alias: pci:v00008086d00004221sv*sd*bc*sc*i*
alias: pci:v00008086d00004220sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
alias: pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
depends: cfg80211,libipw,lib80211
intree: Y
vermagic: 3.2.32 SMP mod_unload modversions 586
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: associate:auto associate when scanning (default off) (int)
parm: auto_create:auto create adhoc network (default on) (int)
parm: led:enable led control on some systems (default 1 on) (int)
parm: debug:debug output mask (int)
parm: channel:channel to limit associate to (default 0 [ANY]) (int)
parm: qos_enable:enable all QoS functionalitis (int)
parm: qos_burst_enable:enable QoS burst mode (int)
parm: qos_no_ack_mask:mask Tx_Queue to no ack (int)
parm: burst_duration_CCK:set CCK burst value (int)
parm: burst_duration_OFDM:set OFDM burst value (int)
parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
parm: bt_coexist:enable bluetooth coexistence (default off) (int)
parm: hwcrypto:enable hardware crypto (default off) (int)
parm: cmdlog:allocate a ring buffer for logging firmware commands (int)
parm: roaming:enable roaming support (default on) (int)
parm: antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
#
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Wed 27 Nov 2013, 14:45    Post subject:  

alias: pci:v00008086d00004220sv*sd*bc*sc*i*
that should be your wireless chip.

'uname -a' in commandline should be enough

Anyway...modinfo shows that there is support for your chip. So...I dont know where the problem lies.

I think you should check with 'dmesg' what it does tell. There could be wireless spesific error messages.
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Wed 27 Nov 2013, 15:18    Post subject:  

Kernal Version is 3.3.32 ?

# uname -a
Linux puppypc12586 3.2.32 #1 SMP Wed Oct 24 10:24:58 GMT-8 2012 i686 i686 i386 GNU/Linux
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Wed 27 Nov 2013, 16:54    Post subject:  

Kernel is 3.2.32.
Next step would be to check what 'dmesg' tells.

You will find the output also from here:
/var/log/messages
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Wed 27 Nov 2013, 19:26    Post subject:  

dmesg:

[12651.575042] ipw2200: Firmware error detected. Restarting.
[13453.618526] ipw2200: Firmware error detected. Restarting.
[13592.858864] ipw2200: Failed to send SSID: Command timed out.
[13594.495499] ipw2200: Failed to send ASSOCIATE: Command timed out.
[13619.068856] ipw2200: Failed to send SSID: Command timed out.
[13718.002848] ipw2200: Firmware error detected. Restarting.
[13798.249321] ipw2200: Firmware error detected. Restarting.
[13950.305342] ipw2200: Firmware error detected. Restarting.


[ 4973.912491] ipw2200: Firmware error detected. Restarting.
[ 5607.662997] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 5608.319665] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 6075.145324] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 6075.816283] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 6159.730819] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 6160.396278] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 8399.692619] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 8400.346054] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9079.625837] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9080.279317] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9170.505974] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9171.159306] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9345.175958] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9345.835955] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9537.329271] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9537.982605] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9586.795934] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9587.449265] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[ 9928.078427] ipw2200: Firmware error detected. Restarting.


[36991.960037] ipw2200: Firmware error detected. Restarting.
[39293.801925] ipw2200: Firmware error detected. Restarting.
[39563.439342] ipw2200: Firmware error detected. Restarting.
[41795.616802] ipw2200: Firmware error detected. Restarting.
[41996.627506] ipw2200: Firmware error detected. Restarting.
[59879.060903] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[59879.727573] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[62215.988091] ipw2200: Firmware error detected. Restarting.
[62330.983623] ipw2200: Firmware error detected. Restarting.
[62404.415052] ipw2200: Firmware error detected. Restarting.


[39293.801925] ipw2200: Firmware error detected. Restarting.
[39563.439342] ipw2200: Firmware error detected. Restarting.
[41795.616802] ipw2200: Firmware error detected. Restarting.
[41996.627506] ipw2200: Firmware error detected. Restarting.
[59879.060903] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[59879.727573] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[62215.988091] ipw2200: Firmware error detected. Restarting.
[62330.983623] ipw2200: Firmware error detected. Restarting.
[62404.415052] ipw2200: Firmware error detected. Restarting.
[62439.002710] ipw2200: Firmware error detected. Restarting.
[62479.861742] ipw2200: Firmware error detected. Restarting.
[62597.608655] ipw2200: Firmware error detected. Restarting.
[62969.795127] ipw2200: Firmware error detected. Restarting.
[63002.878795] ipw2200: Firmware error detected. Restarting.


[81190.349636] ipw2200: Firmware error detected. Restarting.
[81855.274322] ipw2200: Firmware error detected. Restarting.
[81992.570912] ipw2200: Firmware error detected. Restarting.
[82051.818686] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
[82052.478687] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
#

I lost connection after 30 minutes 42 seconds

# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
#

Hovering cursor over network icon I get:
Active interfaces: eth1 RX:285.0MB
(Month:284MB) Tx:10.6MB (Month:10MB)

See no change after running dmesg tail

Disconnect from network
reconnect to network

This time I got:

Failed to connect to any networks.
If you have not yet configured any network interfaces,
you should do so with the Network Wizard.
(debug messages can be found in /tmp/network-connect.log)

Puppy Network Wizard came up on it's own.
Configuring network interface eth0
cheching if interface eth0 is alive...no
interface eth0 doeconfiguring network interface eth0
cheching if interface eth0 is alive...no
interface eth0 does not seem to be plugged in... skipping
configuring network interface eth1
Configuring interface eth1 to network linksys with iwconfig...
/etc/rc.d/rc.network: line 528: 14184 Terminated gtkdialog3 --program NETWIZ_Connecting_DIALOG
cheching if interface eth1 is alive...no
failed to configure wireless interface eth1... skippings not seem to be plugged in... skipping
configuring network interface eth1
Configuring interface eth1 to network linksys with iwconfig...
/etc/rc.d/rc.network: line 528: 14184 Terminated gtkdialog3 --program NETWIZ_Connecting_DIALOG
cheching if interface eth1 is alive...no
failed to configure wireless interface eth1... skipping

/tmp/network-connect.log

LEfor CELL in $CELL_LIST ; do
Get_Cell_Parameters $CELL
# we should have at least some of:
# CELL_ESSID, CELL_FREQ, CELL_CHANNEL, CELL_QUALITY,
# CELL_AP_MAC, CELL_MODE, CELL_ENCRYPTION
# see if it's open or not
if [ "$CELL_ENCRYPTION" = "on" ] ; then
# get only encrypted profiles (might have problems with globbing?)
for PROF in $(ls ${PROFILES_DIR}/${CELL_AP_MAC}.W[EP][PA]*.conf 2>/dev/null) ; do
SUCCESS=""
# unset static ip variables
unset STATIC_IP IP_ADDRESS NETMASK DNS_SERVER1 DNS_SERVER2 GATEWAY
# source it
. "$PROF"
# assign to PROFILE_ names...
assignProfileData
case $PROFILE_ENCRYPTION in
WPA|WPA2)
WPA_CONF="${WPA_SUPP_DIR}/${PROFILE_AP_MAC}.${PROFILE_ENCRYPTION}.conf"
useWpaSupplicant "$WPA_CONF" && SUCCESS="yes"
;;
WEP)
useIwconfig && SUCCESS="yes"
;;
esac
if [ "$SUCCESS" = "yes" ] && sleep 1 && testInterface ; then
# sleep a bit, just in case (net-setup.sh has 5 seconds!)
#sleep 1
# try and get ip address
if try_and_connect ; then
# done! stop everything.
success_message
# clean scan files
rm /tmp/iwscan*.tmp 2>/dev/null
#exit
# move to next interface (to allow more than one)
GOT_ONE="yes"
continue 3
else
failure_message
fi
else # iwconfig/wpa_supp failed
failure_message
fi
done # for PROF in
else # encryption off
# see if it was configured
if [ -f "${PROFILES_DIR}/${CELL_AP_MAC}.Open.conf" ] ; then
# unset static ip variables
unset STATIC_IP IP_ADDRESS NETMASK DNS_SERVER1 DNS_SERVER2 GATEWAY
# source it
. "${PROFILES_DIR}/${CELL_AP_MAC}.Open.conf"
# assign to PROFILE_ names...
assignProfileData
# try connection
if useIwconfig && sleep 1 && testInterface ; then
# sleep a bit, just in case (net-setup.sh has 5 seconds!)
#sleep 1
# try and get ip address
if try_and_connect ; then
# done! stop everything.
success_message
# clean scan files
rm /tmp/iwscan*.tmp 2>/dev/null
#exit
# move to next interface (to allow more than one)
GOT_ONE="yes"
continue 2
else
failure_message
fi
else
failure_message
fi
else # add to list of open networks
OPEN_NETWORKS="$OPEN_NETWORKS $CELL"
fi
fi # if [ "$CELL_ENCRYPTION" = "on" ] ; then
done # for CELL in
# if we got here, we are not connected yet, look at open networks
if [ "$OPEN_NETWORKS" ] ; then
# unset static ip variables
unset STATIC_IP IP_ADDRESS NETMASK DNS_SERVER1 DNS_SERVER2 GATEWAY
for CELL in $OPEN_NETWORKS ; do
Get_Cell_Parameters $CELL
# need to convert to PROFI_...
cellToProfile
if useIwconfig && sleep 1 && testInterface ; then
# sleep a bit, just in case (net-setup.sh has 5 seconds!)
#sleep 1
# try and get ip address
if try_and_connect ; then
success_message
# clean scan files
rm /tmp/iwscan*.tmp 2>/dev/null
#exit
# move to next interface (to allow more than one)
GOT_ONE="yes"
continue 2
else
failure_message
fi
else
failure_message
fi
done #for CELL in $OPEN_NETWORKS
fi
else # if [ -n "$CELL_LIST" ]; then
echo "wireless scan with iwlist failed (no networks found)... skipping interface"
# clean up (kills dhcpcd etc)
cleanUpInterface "$INTERFACE"
ifconfig "$INTERFACE" down
# clean scan files
rm /tmp/iwscan*.tmp 2>/dev/null
# go to next interface
continue
fi
fi
# if we got here, config file exists, but nothing worked
echo "failed to configure wireless interface $INTERFACE... skipping"
ifconfig "$INTERFACE" down
continue


/var/log/messages

Nov 28 03:30:06 puppypc12586 user.warn kernel: [80968.677068] ipw2200: Firmware error detected. Restarting.
Nov 28 03:32:13 puppypc12586 user.info kernel: [81095.389313] usb 1-3: USB disconnect, device number 5
Nov 28 03:33:48 puppypc12586 user.warn kernel: [81190.349636] ipw2200: Firmware error detected. Restarting.
Nov 28 03:44:52 puppypc12586 user.warn kernel: [81855.274322] ipw2200: Firmware error detected. Restarting.
Nov 28 03:47:10 puppypc12586 user.warn kernel: [81992.570912] ipw2200: Firmware error detected. Restarting.
Nov 27 13:47:59 puppypc12586 daemon.info dhcpcd: received SIGTERM, stopping
Nov 27 13:47:59 puppypc12586 daemon.info dhcpcd: eth1: removing interface
Nov 27 13:47:59 puppypc12586 daemon.debug dhcpcd: eth1: deleting default route via 192.168.1.1
Nov 27 13:47:59 puppypc12586 daemon.debug dhcpcd: eth1: deleting route to 192.168.1.0/24
Nov 27 13:47:59 puppypc12586 daemon.debug dhcpcd: eth1: deleting IP address 192.168.1.107/24
Nov 27 13:47:59 puppypc12586 daemon.debug dhcpcd: eth1: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason STOP
Nov 28 03:48:09 puppypc12586 user.info kernel: [82051.818686] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
Nov 28 03:48:10 puppypc12586 user.info kernel: [82052.478687] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
Nov 27 13:48:20 puppypc12586 daemon.info dhcpcd: version 5.1.5 starting
Nov 27 13:48:20 puppypc12586 daemon.debug dhcpcd: eth1: using ClientID 01:00:0e:35:16:ab:40
Nov 27 13:48:20 puppypc12586 daemon.debug dhcpcd: eth1: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
Nov 27 13:48:20 puppypc12586 daemon.debug dhcpcd: eth1: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Nov 27 13:48:20 puppypc12586 daemon.info dhcpcd: eth1: broadcasting for a lease
Nov 27 13:48:20 puppypc12586 daemon.debug dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xe20c928a), next in 3.74 seconds
Nov 27 13:48:24 puppypc12586 daemon.debug dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xe20c928a), next in 7.97 seconds
Nov 27 13:48:32 puppypc12586 daemon.debug dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xe20c928a), next in 16.79 seconds
Nov 27 13:48:49 puppypc12586 daemon.debug dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xe20c928a), next in 32.53 seconds
Nov 27 13:48:50 puppypc12586 daemon.err dhcpcd: timed out
Nov 27 13:48:50 puppypc12586 daemon.warn dhcpcd: allowing 8 seconds for IPv4LL timeout
Nov 27 13:48:50 puppypc12586 daemon.info dhcpcd: eth1: probing for an IPv4LL address
Nov 27 13:48:50 puppypc12586 daemon.info dhcpcd: eth1: checking for 169.254.240.75
Nov 27 13:48:50 puppypc12586 daemon.debug dhcpcd: eth1: sending ARP probe (1 of 3), next in 1.75 seconds
Nov 27 13:48:50 puppypc12586 daemon.info dhcpcd: eth1: offered 192.168.1.107 from 192.168.1.1
Nov 27 13:48:50 puppypc12586 daemon.debug dhcpcd: eth1: sending DHCP_REQUEST (xid 0xe20c928a), next in 3.70 seconds
Nov 27 13:48:50 puppypc12586 daemon.info dhcpcd: eth1: acknowledged 192.168.1.107 from 192.168.1.1
Nov 27 13:48:50 puppypc12586 daemon.info dhcpcd: eth1: checking for 192.168.1.107
Nov 27 13:48:50 puppypc12586 daemon.debug dhcpcd: eth1: sending ARP probe (1 of 3), next in 1.88 seconds
Nov 27 13:48:52 puppypc12586 daemon.debug dhcpcd: eth1: sending ARP probe (2 of 3), next in 1.67 seconds
Nov 27 13:48:54 puppypc12586 daemon.debug dhcpcd: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Nov 27 13:48:56 puppypc12586 daemon.info dhcpcd: eth1: leased 192.168.1.107 for 86400 seconds
Nov 27 13:48:56 puppypc12586 daemon.debug dhcpcd: eth1: adding IP address 192.168.1.107/24
Nov 27 13:48:56 puppypc12586 daemon.debug dhcpcd: eth1: adding route to 192.168.1.0/24
Nov 27 13:48:56 puppypc12586 daemon.debug dhcpcd: eth1: adding default route via 192.168.1.1
Nov 27 13:48:56 puppypc12586 daemon.debug dhcpcd: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Nov 27 13:48:56 puppypc12586 daemon.debug dhcpcd: eth1: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Nov 27 13:48:56 puppypc12586 daemon.info dhcpcd: forking to background
Nov 27 13:48:56 puppypc12586 daemon.debug dhcpcd: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Nov 27 13:48:58 puppypc12586 daemon.debug dhcpcd: eth1: sending ARP announce (2 of 2)
Nov 27 14:38:53 puppypc12586 daemon.info dhcpcd: received SIGTERM, stopping
Nov 27 14:38:53 puppypc12586 daemon.info dhcpcd: eth1: removing interface
Nov 27 14:38:53 puppypc12586 daemon.debug dhcpcd: eth1: deleting default route via 192.168.1.1
Nov 27 14:38:53 puppypc12586 daemon.debug dhcpcd: eth1: deleting route to 192.168.1.0/24
Nov 27 14:38:53 puppypc12586 daemon.debug dhcpcd: eth1: deleting IP address 192.168.1.107/24
Nov 27 14:38:53 puppypc12586 daemon.debug dhcpcd: eth1: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason STOP
Nov 28 04:39:46 puppypc12586 user.info kernel: [85148.448376] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
Nov 28 04:39:47 puppypc12586 user.info kernel: [85149.101709] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
Nov 28 04:41:17 puppypc12586 user.info kernel: [85239.911702] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
Nov 28 04:41:18 puppypc12586 user.info kernel: [85240.565036] tg3 0000:02:00.0: BAR 0: set to [mem 0xfaff0000-0xfaffffff 64bit] (PCI address [0xfaff0000-0xfaffffff])
Nov 28 05:17:53 puppypc12586 user.warn kernel: [87435.600488] ipw2200: Firmware error detected. Restarting.
Nov 28 05:21:55 puppypc12586 user.warn kernel: [87677.401611] ipw2200: Firmware error detected. Restarting.
Nov 28 05:23:37 puppypc12586 user.warn kernel: [87779.789706] ipw2200: Firmware error detected. Restarting.
Nov 28 05:28:27 puppypc12586 user.warn kernel: [88069.551387] ipw2200: Firmware error detected. Restarting.
Nov 28 05:39:45 puppypc12586 user.warn kernel: [88747.815154] ipw2200: Firmware error detected. Restarting.
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.597430] usb 1-3: new high-speed USB device number 6 using ehci_hcd
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.725587] usb 1-3: New USB device found, idVendor=13fe, idProduct=3e00
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.725592] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.725596] usb 1-3: Product: USB DISK 2.0
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.725599] usb 1-3: Manufacturer:
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.725602] usb 1-3: SerialNumber: 07C10302CDC7053A
Nov 28 07:16:57 puppypc12586 user.debug kernel: [94579.727938] usb-storage: device found at 6
Nov 28 07:16:57 puppypc12586 user.info kernel: [94579.730301] scsi6 : usb-storage 1-3:1.0
Nov 28 07:16:57 puppypc12586 user.debug kernel: [94579.730393] usb-storage: waiting for device to settle before scanning
Nov 28 07:16:58 puppypc12586 user.notice kernel: [94580.809786] scsi 6:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 4
Nov 28 07:16:58 puppypc12586 user.notice kernel: [94581.289018] sd 6:0:0:0: [sdb] 7579008 512-byte logical blocks: (3.88 GB/3.61 GiB)
Nov 28 07:16:58 puppypc12586 user.notice kernel: [94581.289635] sd 6:0:0:0: [sdb] Write Protect is off
Nov 28 07:16:58 puppypc12586 user.debug kernel: [94581.289639] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
Nov 28 07:16:58 puppypc12586 user.err kernel: [94581.290260] sd 6:0:0:0: [sdb] No Caching mode page present
Nov 28 07:16:58 puppypc12586 user.err kernel: [94581.290264] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Nov 28 07:16:58 puppypc12586 user.debug kernel: [94581.291173] usb-storage: device scan complete
Nov 28 07:16:58 puppypc12586 user.err kernel: [94581.294263] sd 6:0:0:0: [sdb] No Caching mode page present
Nov 28 07:16:58 puppypc12586 user.err kernel: [94581.294268] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Nov 28 07:16:58 puppypc12586 user.info kernel: [94581.313052] sdb: sdb1
Nov 28 07:16:58 puppypc12586 user.err kernel: [94581.316139] sd 6:0:0:0: [sdb] No Caching mode page present
Nov 28 07:16:58 puppypc12586 user.err kernel: [94581.316144] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Nov 28 07:16:58 puppypc12586 user.notice kernel: [94581.316149] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Thu 28 Nov 2013, 00:50    Post subject:  

ipw2200: Firmware error detected. Restarting.
usb 1-3: USB disconnect, device number 5

Maybe you should try to hunt newer - another - better working firmware package for ipw2200 kernel module.

If you find it, you can place them straight to /lib/firmware....which bypasses Puppy /lib/modules/all-firmware relocating system.
Back to top
View user's profile Send private message 
ardvark


Joined: 01 Jul 2013
Posts: 1009
Location: USA

PostPosted: Thu 28 Nov 2013, 05:57    Post subject:  

pemasu wrote:
Maybe you should try to hunt newer - another - better working firmware package for ipw2200 kernel module.


Would here work? Smile

EDIT: Guess not, the download links are broken. If anyone can extract an rpm (could P7zip 9.04 do it,) there is this page. Debian also has a download page, if it helps at all. Question

Regards...

_________________
Our Lord and Savior Jesus Christ loves and cares about you most of all!

PLEASE READ! You don't have to end up here!
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Fri 29 Nov 2013, 12:55    Post subject:  

All the downloads for the Intel firmware are .exe. When I use them w/the NDISwrapper, the wrapper informs me that it can't use a .exe. It wants a .inf file

Is there a way to extract the .inf from the .exe installer? How do I know which .inf to use?

I am wondering if there is something wrong with the retroprecise NDISwrapper. I have used a wrapper with Ubuntu 10.04, and now Mint 14. It just worked.
Back to top
View user's profile Send private message 
borgward

Joined: 18 Jan 2006
Posts: 28
Location: Austin, Texas

PostPosted: Fri 29 Nov 2013, 15:20    Post subject:  

Just downloaded ICS_Dx32.zip and extracted files from it

I tried NETw532.INF and w29n51.INF. After using Ndiswrapper I got invalid driver message for each of them.

The D600 was running XP until the HDD went south and the laptop was given to me, so I think an XP driver should work. How do I determine which .INF works.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [14 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware » Networking » Wireless
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1446s ][ Queries: 12 (0.0045s) ][ GZIP on ]