Three-Headed Dog 5.2.8.005 Updated APR 25 2012

[jim3630]

frugal manual hdd install to ext4. as noted quickpet and browser not working. installed broadcom pet for my troublesome wl.ko driver. needed frisbee this time to make wifi connect. neither sns or connection wizard worked.


Information about this interface:
Interface: eth1 Driver: wl Bus: pci MacAddress: AC:81:12:1D:A9:5E
Description: x

STEP1a: ifconfig eth1 up
STEP1b: iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:19:E4:4B:D3:19
ESSID:"2WIRE789"
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:4/5 Signal level:-59 dBm Noise level:-99 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 02 - Address: 64:0F:28:37:59:31
ESSID:"2WIRE425"
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:0/5 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
STEP1c: ifconfig eth1 down
STEP2: iwconfig eth1 mode managed
STEP3: iwconfig eth1 channel 10
STEP4: iwconfig eth1 essid "2WIRE789"
STEP5: iwconfig eth1 key restricted 9xxxxxxxxxxxx
STEP5a: ifconfig eth1 up

ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:72 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


STEP5: iwconfig eth1 key open 9977453890
STEP5a: ifconfig eth1 up

ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:72 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



*********************************************************
LAST 10 LINES of /var/log/messages:
Sep 17 02:50:33 puppypc user.warn kernel: Console: switching to colour frame buffer device 200x56
Sep 17 02:50:33 puppypc user.info kernel: fb0: inteldrmfb frame buffer device
Sep 17 02:50:33 puppypc user.info kernel: drm: registered panic notifier
Sep 17 02:50:33 puppypc user.info kernel: acpi device:02: registered as cooling_device2
Sep 17 02:50:33 puppypc user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
Sep 17 02:50:33 puppypc user.info kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Sep 17 02:50:33 puppypc user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Sep 17 02:50:33 puppypc user.info kernel: HDMI hot plug event: Pin=6 Presence_Detect=1 ELD_Valid=0
Sep 15 20:51:05 puppypc user.notice powerapplet: Abort, no /proc/apm or acpi/info
Sep 15 20:51:07 puppypc user.notice powerapplet: Abort, no /proc/apm or acpi/info

[jim3630]

installed lucid 525 seamonkey 2.3 pet. lots of errors.

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

[playdayz]

I have withdrawn Three-headed Dog version 2 until it is decent. I apologize for the inconvenience.

[jim3630]

playdayz no problem

FYI got the same error message when installed ff 6 lucid pet

[James C]

I have withdrawn Three-headed Dog version 2 until it is decent. I apologize for the inconvenience.

Other than Quickpet showing a nice dialog box, no problems here with the latest. Fresh frugal install.
No problems with SeaMonkey......posting from it now.regular SeaMonkey 2.3 pet out of the PPM.

You could just disable the "drivers" part of Quickpet .....luckily 01micko took care of that for Lucid Retro.Wouldn't want users grabbing the wrong drivers.

[playdayz]

jim3560, Where are you seeing the SM and FF messages? Were you starting them in a terminal?

Other than Quickpet showing a nice dialog box, no problems here with the latest. Fresh frugal install.
No problems with SeaMonkey......posting from it now.regular SeaMonkey 2.3 pet out of the PPM.

Thanks James C. it seems like a good one so I think it will be back. I didn't disable Quickpet--it disabled itself because it checks for what version of Puppy is being used and it did not recognize 3HD I have it running but it fails in downloading, so I might need 01micko.

[James C]

No problem with Firefox either.Took me a minute to get it downloaded.

EDIT:

No messages launching either Firefox or SeaMonkey from the terminal......browsers just launch.

[majorfoo]

Realize you have withdrawn 3hd-001, however, just completed full install to ext4 partition

Booted to desktop -ok
sound - ok
auto connected to internet on full install - did not on boot of live cd
seamonkey-2.3-lucid525.pet ok no problems - ran from desktop and from command line

added following from my save partition
abiword 2.90 -ok
xorg_high-1.1
xscreensaver-5.14
wbar-with setup-1.33-lucid-cd1
evince-2.30.3
puppybrowser-1.1-lucid
flashplayer 10-3-181-34-lucid
shermans aquarium-3.01
bibletime-2.72
pwidgets-2.3.6
sfs install-0.12
audacious-3.02
tcl_tk_plus.sfs

everything work great on my hp pentium 4, 2.8ghz, 2gb mem
20gb hd 3 ext4 partitions, 1 storage partition

look forward to next version

majorfoo

[jim3630]

jim3560, Where are you seeing the SM and FF messages? Were you starting them in a terminal?
.

showed those errors when opened from menu and when clicked on new link. console showed no errors opening or while running.

[playdayz]

showed those errors when opened from menu

Oh, where did it show them? And, had you installed and uninstalled any pets before that? Thanks for your help.

[James C]

Thanks James C. it seems like a good one so I think it will be back. I didn't disable Quickpet--it disabled itself because it checks for what version of Puppy is being used and it did not recognize 3HD I have it running but it fails in downloading, so I might need 01micko.

Might as well put it back up........other than the Quickpet thing I can see no other problems.
My usual fresh manual frugal install......everything working on initial boot.Installed SeaMonkey and Firefox....no problems.Went to minimal icons and JWM....still don't like Openbox.

[James C]

I didn't disable Quickpet--it disabled itself because it checks for what version of Puppy is being used and it did not recognize 3HD I have it running but it fails in downloading, so I might need 01micko.

I believe runtt21 ran into the same thing with Macpup too.

[playdayz]

Might as well put it back up..

Oh, I will tomorrow. Instead of fighting for the name 3HD I went back to Luci--Quickpet is happy again

Thanks.

See, I'm thinking that with a couple of versions, it could be a good foundation for whatever kernel one wanted to use.

[James C]

Been running for a while and doing the usual tweaks.....everything looking fine so far.Everything has survived several reboots as well.

[jim3630]

showed those errors when opened from menu

Oh, where did it show them? And, had you installed and uninstalled any pets before that? Thanks for your help.

playdayz a message box is where, if I wasn't clear no errors from the console. only pets installed broadcom wl k2.6.37.6 spup and frisbee from the menu.

did try sm 2.4 from slacko first, did not work then uninstalled before installing lucid sm.

[01micko]

hi jim3630

Many slacko pets will not likely work in lucid because of the later versions of gtk/gdk/cairo/pango/pixman. I link against all these when compiling seamonkey/firefox to shave a couple of M off the size.

As for quickpet woes I can make a new version if need be. When I think about it I could have saved some grief if I had of tested for DISTRO_BINARY_COMPAT instead of DISTRO_FILE_PREFIX, it would have been far more general and puplet makers could then make their prefix whatever they like. It even tripped me up when I went from "spup" to "slacko". Fortunately that one didn't get released .

I know the embarrassment though.. spup-054 lasted all of 30 minutes when nooby reported the "play" icon on the desktop was broken (among several other things). Again, fortuitously, it was early enough in the day for me to do a rebuild.

Cheers!

[jim3630]

hi jim3630

Many slacko pets will not likely work in lucid because of the later versions of gtk/gdk/cairo/pango/pixman.

hi 01micko even un-installed slacko pets seems can be bad medicine in lucid.

[tasmod]

F-Prot and Xfprot.

Sorry guys, I missed a directory in F-prot so Xfprot errored out with binary not found. It was a path issue.

New version of F-prot further back replacing the incorrect version.

Xfprot is OK. BUT please remember to run 'F2 Update' button for latest definitions first.

Please test. Thanks.

[tempestuous]

Should Three-Headed Dog try to accommodate more drivers and firmware, even to the extent of growing by 5MB?

playdayz, it's really a question of WHAT additional drivers are available, and which should be included.
The vendor-provided Ralink and Realtek wifi drivers are prime candidates for inclusion in Puppy ....
but the separate dotpets of these drivers that I provided for Puppy 5.1 to 5.2.8 required extensive testing by various forum members before I knew which particular driver versions worked, and which didn't.
The vendor-supplied Ralink rt3070sta driver - version 2.3.0.1, for example, works really well with the 2.6.33.2 kernel in Puppy 5.1 to 5.2.8. But it took months of of trial and error before we worked this out. And it's a messy situation - this driver claims an overlapping range of device ID's already claimed by the standard rt2870sta and rt2800usb drivers already in Puppy.

Now that we're dealing with a new kernel in Puppy 529, it's uncertain whether this driver is still the best option, or whether the more recent vendor-supplied rt3370sta driver will be best, or whether the standard rt2800usb driver is now stable and the vendor-supplied driver is unnecessary! There are just too many question marks, so I think the Ralink and Realtek third-party wifi drivers should remain separate driver dotpets.

So my suggestions for additional drivers are just these important two:

- There's a new Broadcom wifi driver in the 2.6.37.6 kernel which you didn't enable, and I think it should be.
It's called brcm80211 and it's in the "staging" section of the kernel configuration.
This will require additional firmware, which I can source for you.
Hopefully this will fix the problem of modern Broadcom wifi devices not working with the standard b43 driver, and the proprietary "wl" driver will no longer be a necessary last resort.

- "Fusion" SCSI interface support.
For many years Puppy has included extensive SCSI interface support, but a glaring omission has been "Fusion MPT" SCSI support, mainly for SCSI interfaces by LSI. These are found on Dell PowerEdge servers, for example; one of the most common SCSI-equipped computers on the market. The kernel configuration option I'm referring to is found at:
Device Drivers > Fusion MPT device support
Enabling this option will change the kernel image slightly, and it will then offer the option of adding 3 (necessary) kernel modules:
mptspi
mptfc
mptsas

[playdayz]

Three-Headed Dog Version 2 Take 2 is posted in the first message of this thread. Thank you.