Puppy Linux Discussion Forum

[jemimah]

I will add CONFIG_B43_FORCE_PIO to the next kernel and see if that will fix it.

[Roy]

Thanks!

Looking forward to trying it.

-Roy

[JustGreg]

I have an Intel Classmate with a 800 by 480 (7 inch) screen, Celeron 900 MHz processor, 512 Mbytes of ram and 2 Gbyte USB flash drive. Fluppy install correctly and runs. I did find the battery monitor did not work correctly. It detected the use of AC power, but, did not show the correct battery condition. The monitor has the battery discharged at all times and not charging. I also tried Lucid Puppy 5.0 and the battery monitor with Lucid worked correctly. The battery was charging properly.

I do not think the issue of the Classmate and battery monitor is a major one and needs to be fixed. In case of the Classmate and its small keyboard, I can only use it for a limited period before I give up typing and go to hunt and peck. This post is to tell how Fluppy works on different hardware.

[jemimah]

Out of curiousity what are the contents of /proc/acpi/battery/BAT0/state?

There is a script in /root/Startup that decides whether to run vattery or vattery-old-version. Vattery-old-version works in some cases where the battery reports unexpected things, so you could try running it and see if that fixes it and I can adjust the script if it works.

[JustGreg]

I checked /proc/acpi/battery/BAT0/state and found there is no BAT0 directory. However, there is a BAT1 directory with all the information. So the problem is the Vattery is looking in wrong directory. Will the vattery-old look at the correct directory?

Yes, I have tried both vattery an vattery-old-version in console terminal window. The vattery-old-version fails with an error saying no BAT0 directory. The vattery program just reports the battery is discharge due to the lack of the information. This is a ClassMate specific issue to me since everything else has BAT0.

[jemimah]

That is pretty weird. I don't think either vattery is setup for that. I bet acpitool can figure it out, try 'acpitool -B'. At some point I should make a SuperVattery that tries all the methods.

[JustGreg]

yes, jemimah, acpitool does work. If acpitool -b is used then the information is all on one line to the std output. With acpitool -B, one gets multiple lines of output.. I tried to make a symlink from BAT1 to BAT0, but, the proc directory will not allow it. Something to think about in the future.

I did play with acpitool. It is neat. It provides a lot of information.

[jamesbond]

jemimah,

Just trying out fluppy 002 in my newish laptop. Same problem with Roy - wireless firmware is not there (I copy from quirky), it's not extracted automatically (I untarrred myself). Apart from that, everything seems to be in order

Thanks!

[smokey01]

jemimah, fluppy is just brilliant on my kogan netbook.

Up until fluppy I couldn't be bothered using it but now I use it quite often. Many thanks.

Are you aware of any scheduling or planning software that will work with puppy? Osmo is nice but it doesn't seem to have a planning function. I would like something simple. It doesn't have to be as complex as MS Project. I did see something called ganttpv but I'm not sure if it works on puppy.

Regards

Smokey

[jemimah]

[gronos04]

Hi Jemimah
Have been running fluppy002 for a few days on my Panasonic Toughbook cf-18

As with a number of others

[jemimah]

[smokey01]

[TomRhymer]

I just found out something about the 'boot error' problem. It's not just with the save file, adding any file to the flash drive after install causes it. This happens if you add a file either in Linux or using Windows. Rerunning the Bootinst program fixes it, but any time you add a file, you need to rerun it.

[jemimah]

Fluppy03 has been posted. Hopefully all the firmware is there now.

This also has the Xorg upgrade I did for Puppeee. This will enable PineTrail chipsets to workl, and some other cool features. All Xorg drivers are now installed.

I also added the acerhdf module and the nvidia module to the kernel.