Puppy Linux Discussion Forum

[irishrm]

Jamesbond:
Did the reboot-did the scan-did the reconnect but still no connection.

BC-wl status:
Start at boot: yes
Currently running: yes
Control file: 30-BC-wl.

I have a working install of fatdog 510 and 610.
I also have precise and slacko installs with the wl driver working with frisbee.

I may get a better result with a later release of 620.
Thanks to yourself and kirk for your help.

irishrm.

[jamesbond]

irishrm,

If you don't mind, one last thing - can you dump the output of "dmesg" from terminal here? We may see something that may help. Broadcom isn't a good wireless chips to have, I regret to say (and I'm saying this as one who owns one too) The proprietary "wl" drivers haven't been updated in the last two years (check it yourself here: http://www.broadcom.com/support/802.11/linux_sta.php), I think with the intention that the open-source driver will take over, but the open-source driver isn't up to par yet. So what has been done on the "wl" drivers are patches upon patches upon patches by people, without knowing that broadcom is doing internally within their binary blob. Sometimes you hit jackpot and it works, but it then we hit issues like yours.

JustGreg,

I remember something - those "special keys" buttons are problematic. Some of them are "hardcoded" into ACPI bios - they always work whatever the OS you install (even on no OS at all). Some of them are wired through ACPI events. Some of them are wired through ACPI events *only* if you have the right wmi driver loaded (in your case, probably hp_wmi as you said). Some of them are routed through normal keyboard driver, but they are extremely broken (e.g. button generates keypress without corresponding keyrelease, or generates very funny keycode which requires mapping etc). In the latter cases, one needs to capture the "event" and then run a script to do something (e.g."rfkill" to turn on/off the devices). Try to run "xev" first and when the mouse is over the xev window, press F9 key and tell me what you've got. Also try to run "evtest" from terminal, then choose your keyboard input, then press your magic F9 key and see how it goes.

[irishrm]

Thanks jamesbond.

I'm attaching dmesg.

Don't waste any more time on trying to get a fix.
I have plenty to be going on with. Maybe it might work in the next release.

irishrm.

[JustGreg]

Thanks for the information, JamesBond.

The savefile directory was on an ext2 filesystem partition. Now that I know the spot directory has the needed files, I can try it again and make any changes as needed.

I did the two tests on the key. It turns out the special key is the "F12" key. The F12 key press is not detected by either xev or evtest. I will have to remember those two utilities. The good news is the wifi module can be control by rfkill either rfkill block wlan or rfkill unblock wlan. That problem is solved.

I have been having x server start up "hiccups" with the Radeon driver. Sometimes, it does not start up correctly. I get the mouse cursor with either a white screen or one with no display (cursor can be seen). Fatdog does not have the utility reportvideo like other puppies. It does help with these types of problems. I have tried the Vesa driver and it failed. I have a couple of ideas I will try to see if I get a better information on what is failing to start.

Some additional information

I tried using the older ATI driver to see if the problem would go away. It did not. When the driver/ xserver seem to fail to start, one needs to use the power key to get out of the hung system. This loses any logs. I did find if I do a manual (pfix=nox) start of the x server then it always works. It may take longer to display the desktop, but, it does start. I did notice one item with pfix=nox. The console seems to stop at the command "Starting HAL daemon /usr/sbin/hald --daemon=yes" One needs to press the "enter" key to get the console prompt. I do not know if this is an issue. But, it was the only thing that caught my attention. I hope this helps.

[smokey01]

JustGreg,

The report-video here seems to work ok.
http://www.murga-linux.com/puppy/viewtopic.php?p=677225&sid=43648053dc262ebeb04f1cf66edee5fc#677225

[JustGreg]

Thanks Smoke01! I have down loaded the pet and will try it out. It is nice to know that report-video is not arch dependent. Thanks again. I will report how it worked here.

08:48 EST, The pet loaded and started. However, it did not report any information. It may be do to fatdog64 does not have same xorg configuration as the other puppies. The xorg.conf file does not have a video section that lists the driver. It is not clear to me how the graphics video is started. Thanks for the information on the pet.

[JustGreg]

I have been starting fatdog64 620BETA with the pfix=nox option to insure the x server starts correctly. When I have 620BETA start directly into x server, the x server fails to start correctly. There is no video display and it does not respond to either ctrl alt backspace or ctrl alt delete key commands. The mouse cursor is present and responds correctly. I have tried the ATI driver with the same results. It seems something is interfering with the startup processes (maybe the hal daemon process and window manager?).

I also delete the existing save file and started with nosave file. BETA620 initialized correctly with a x server and window manager. I did create a save directory. I do like the save directory. It does work well. I tried a restart and x server failed. Back to nox option for start up.

I can not get any of the logs to see what is failing.

[kirk]

[JustGreg]

Answers to your questions:

[kirk]

[JustGreg]

Thank you Kirk for the reply. I had another failure to start from power on (cold boot). I have increased the sleep time to 5 seconds. It seems to help. I have tried three cold starts in a row with about 5 minutes between the shut off and start. Not a single failure. I will keep an eye on it. Thanks again for the help.

[Ray MK]

Fatdog64 620beta1

Manual frugal to an ntfs partition and booting via grub4dos on an SDcard.

Finally got hold of a 64bit laptop again (sadly the screen is cracked) so using an old ProView LCD monitor that seems to work quite well.

The laptop is an E732 (Emachines / Acer) with an i3proc. and 2gig ram.

Fantastic Puppy - so fast - it screams.

Boots in seconds - wifi seems ok and all the basics seem fine OOTB.

Many thanks to kirk, james bond & others for helping to make what is probably the best 64bit distro on the planet.

Hinfo report FYI. Very best regards - Ray

[nooby]

Seamonkey in this lastest version seems different to the one
in 611. Local htmlfiles works as expected in the old FatDog
but totally fails in the new. I dl from smokey because the
other server was extremely slow some 63kb instead of 3MBsec

I trust the iso are same on both?