Page 7 of 10

Posted: Mon 24 Aug 2009, 20:38
by sinc
i mentioned this a couple pages back but i had wireless issues. I apparently have to use the b43legacy driver and it doesn't work on my system with the firmware that is included. I copied the firmware package over from 4.21 and it worked so-so but at least it worked.
Thanks.

LAN Printing No Longer Working

Posted: Mon 24 Aug 2009, 22:45
by arby
Well now this can be in the right thread anyways.

I setup a network printer (HP LaserJet 4000) via the CUPS interface.
It says it's successful and the 4000 appears in the print dialog boxes.

But, puppy-4.3beta1-k2.6.29.6-v423.iso appears to print only browser
generated pages; the CUPS test page and Sea Monkey browser pages.

Viewing 'lpstat -t', shows the editors in Puppy aren't generating
any print jobs, while Sea Monkey and CUPS setup page are.

Editors Abiword, Medit & Nico lock up the system. Any attempt to click
on the printer, from Abiword, medit or Nico freezes the application
and eventually requires powering off the computer.

Using the same hardware, identical setup and identical network,
puppy 4.12 prints fine, Puppy 4.3 beta doesn't print via LAN at all.

Posted: Tue 25 Aug 2009, 01:44
by jakfish
Arby,

Must be a kernel thing, b/c w/ the 4.3beta1 and the older kernel, I print fine via LAN/Samba to an HP printer (6500 Wireless) with Asus EEE 900. I can print from any app, including MS Word 97 running in Wine.

Jake

Posted: Tue 25 Aug 2009, 02:03
by 01micko
Has any one noticed Puppy Browser not working? Am I the only one? I must have broken it but I've no Idea how. Will do a pfix=ram and see...

:oops: Nope, it's ok, I broke it somehow...

Updated Linuxant HSF/HCF/DGC modem drivers

Posted: Tue 25 Aug 2009, 04:16
by rerwin
Attached is a dotpet made from the Linuxant drivers recompiled for the latest (patch2) kernel 2.6.29.6. Please try this if you have one of those modems. I have sent the source code to Barry.

UPDATE 8/27/09: I have replaced the dotpet with a better version for beta2. I have one further update to make to the firmware tarballs, to simplify them but retain their current functionality.

UPDATE 8/28/09: I have upgraded the dotpet with further refinements to the firmware tarballs. I believe I have solved all the issues I have been working on for beta2. Please accept this as my contribution to beta2.
Richard

Re:LAN Printing No Longer Working

Posted: Tue 25 Aug 2009, 05:13
by arby
Thanks jakfish, you appear to be correct.
It is the newer kernel.

puppy-4.3beta1-k2.6.25.16-v423.iso prints via LAN successfully.

puppy-4.3beta1-k2.6.29.6-v423.iso does not.

Posted: Tue 25 Aug 2009, 11:26
by jakfish
Arby, this is an important bug. Can anybody confirm it?

Jake

Posted: Tue 25 Aug 2009, 12:55
by BarryK
Message for trio, or anyone else who has the problem of the 'b43' firmware not getting installed.

Please run this script (gunzip it first!) and post the output log file here.

Posted: Tue 25 Aug 2009, 13:08
by BarryK
Trio requested my 'Pcur' cursor selector for testing.

Install xcur2png pet pkg.

gunzip pcur.gz and place at /usr/sbin

place default_left_ptr.png at /usr/local/lib/X11/mini-icons

Run pcur.

Re:LAN Printing No Longer Working

Posted: Tue 25 Aug 2009, 13:15
by BarryK
arby wrote:Thanks jakfish, you appear to be correct.
It is the newer kernel.

puppy-4.3beta1-k2.6.25.16-v423.iso prints via LAN successfully.

puppy-4.3beta1-k2.6.29.6-v423.iso does not.
Okay, the next thing for you guys to do is figure out why :)

Posted: Tue 25 Aug 2009, 13:30
by trio
Barry,

Thanks for the response

1. Pcur is great, but default folder should not be in the list also, same as Rox
2. b43 issue, I have to get back to you tomorrow, I don't have the computer with b43 with me now (it's 8.30 PM now here :wink: )

regards

Posted: Tue 25 Aug 2009, 18:41
by sinc
for the b43 issue - please tell me where the output log file is or how to retrieve it and i will post it here. i'm more than happy to report back just not sure exactly what to post. thanks.

Posted: Tue 25 Aug 2009, 19:09
by sinc
i don't know how to copy and paste from a terminal screen but here are 2 screenshots encompassing the output from the terminal when i ran the b43_test script above. thanks.

Posted: Wed 26 Aug 2009, 03:37
by Flash
4.3 beta 1 SeaMonkey closed on me once when I accidentally hit the Insert key (I'm pretty sure that was the key I hit.) I don't remember what I was doing at the time. Probably composing a message in the Puppy Linux Forum.

SeaMonkey has also closed several times while Flash junk was loading. I don't know which version of Flash is supposed to be in 4.3 beta 1 I have 10.0 r32.. I tried to install Flash 10 from the Adobe site before I upgraded my multisession DVD to 4.3 beta 1, so it's possible that the Flash I have is not the one that's supposed to be in 4.3 beta 1.

The sound is messed up when I try to play Flash stuff, such as YouTube videos. Not all the time, but most of it.

All the problems I have with 4.3 beta 1 seem to have to do with Flash. Other than that, it's great. :)

Posted: Wed 26 Aug 2009, 03:39
by trio
Barry,

here's b43log (already copied b43 folder in pup_save). I will boot with pfix=ram and post another b43.log

Posted: Wed 26 Aug 2009, 03:51
by trio
Barry,

Here's another one with pfix=ram

Filenames of remastered puppy

Posted: Wed 26 Aug 2009, 05:05
by shinobar
For the main file names of remastered puppy,
the puppyinstaller allows, say 'ppa4-423ja.sfs'.
It writes '${DISTRO_FILE_PREFIX}-${NEWVER}*.sfs".

But init in initrd.gz does not allow. At line 438 and anywhere it writes
'${DISTRO_FILE_PREFIX}-${DISTRO_VERSION}.sfs'.

And bootflash at line 436, '*-[0-9][0-9][0-9].sfs'.

sudo

Posted: Wed 26 Aug 2009, 08:08
by Skeptic
Will Puppy 4.3 have sudo by default?
It's not safe to run as root by default.

Posted: Wed 26 Aug 2009, 09:15
by gposil
How is it not safe to run as root on a R/O file system?

Posted: Wed 26 Aug 2009, 11:44
by Skeptic
I was talking about full installations.
Running as root from the live-cd is OK in my opinion.