(old)Puppy Linux Discussion Forum

Back light to work?
Your screen is black?

With the 855gme processor I choose the i810 option during
xorg setup.

let me rephrase, the adjustment for the back light fails to function. It is set on low and does not respond to the adjustment button.


X seems to be working okay, it is just I cannot turn the brightness up.

Thanks

Frank Cox, mostly the back-light function is controlled by buttons as you say, or in the BIOS.
I don't think Wary 5.0 has code to do this.

Béèm wrote:Frank Cox, mostly the back-light function is controlled by buttons as you say, or in the BIOS.
I don't think Wary 5.0 has code to do this.

My tablet has a button I always use for the brightness on the LCD frame. It works in every distro I have ever tried , windows, numerous Ubuntu derivatives, lucid , 4.2 . 431 and others I have forgotten but not in Wary so I doubt it has anything to do with the bios, that would affect the others as well. There is certainly the possibility I am wrong but it seems it has to be a bug in Wary, fortunately it is not a big problem .

Fortunately there is a second method of adjusting the brightness, FN F8 and when I remembered that and tried it it worked .


Thanks anyway

Any ideas on the wireless?

pskin wrote:Wary 5.0 is basically working 99% on edubook.

Some issues are:
1) There is no rt3070sta wireless driver for edubooks that came with
adapters that need that. Instead the rtx2800 module (which does not seem to work) is loaded. If this is blacklisted, then a version of rt2870 is loaded on next boot, which also seemed not to work. However, one can blacklist both modules and compile the rt3070sta module from the source downloaded from ralink. Then wireless works.

2)The flash plugin crashes SeaMonkey (e.g. youtube.) This was noted of
wary 093 on Barry's blog. I tried simply to
install a different version of the plugin (I tried version 10.1r102,
the latest available from the Adobe site) and it has not crashed so far.

On Barry's blog, he also mentioned that some things such as ffmpeg
and libvpx may need to be recompiled. Certainly, ffmpeg
gives an Illegal Instruction error at the moment.

-pskin

Yes, it would be good if someone took on a remaster of Wary that works 100% with the Gecko Edubook and variants.

As far as I can recall, the only pkgs not compiled for a 486 CPU are ffmpeg and libvpx ...but I am not sure about mplayer. These were configured for a 686 CPU as otherwise the 'configure' script wouldn't use the MMX instructions -- even though MMX was introduced with the 486. Which was annoying, maybe I could have hacked the 'configure' script.

I think that I posted some notes on how to compile ffmpeg, it can be configured for a 486 CPU and recompiled.

Adobe Flash -- perhaps the older version 9 player would work?

BK wrote:

As far as I can recall, the only pkgs not compiled for a 486 CPU are ffmpeg and libvpx ...but I am not sure about mplayer. These were configured for a 686 CPU as otherwise the 'configure' script wouldn't use the MMX instructions -- even though MMX was introduced with the 486. Which was annoying, maybe I could have hacked the 'configure' script.
I think that I posted some notes on how to compile ffmpeg, it can be configured for a 486 CPU and recompiled.

Barry, Thanks, I found your blog entry about configuring ffmpeg.
Am I right in thinking that I should configure it for 486 and that
I do not want to use MMX since the Vortex86MX does not support it?
Or am I mistaken and MMX is supported?

I'll have a go at remastering wary for edubook if I can get these few things compiled.

-pskin

I have know spent nearly a whole day trying to get the wireless to work in Wary and have come to the conclusion it is a kernel problem and there is no way to overcome it.
Hope 431 is supported a while longer.

Frank Cox wrote:I have know spent nearly a whole day trying to get the wireless to work in Wary and have come to the conclusion it is a kernel problem and there is no way to overcome it.
Hope 431 is supported a while longer.

I have the same wireless card and don't have problems; not likely
to be a kernel issue.

Try a 098 or earlier wary; the extended pcmcia and usb module
loading may have something to do with it; a wild guess.

Sometimes it may switch interfaces if more than one install is on
the drive. A reboot and second attempt may work.

Is there a delta file, to convert Wary104 to 5-final .iso?

rjbrewer wrote:and don't have problems; not likely
to be a kernel issue.

Try a 098 or earlier wary; the extended pcmcia and usb module
loading may have something to do with it; a wild guess.

Sometimes it may switch interfaces if more than one install is on
the drive. A reboot and second attempt may work.

Are the older Warys going to be much different ? 431 works fine on the Tablet.

Frank Cox wrote:

rjbrewer wrote:and don't have problems; not likely
to be a kernel issue.

Try a 098 or earlier wary; the extended pcmcia and usb module
loading may have something to do with it; a wild guess.

Sometimes it may switch interfaces if more than one install is on
the drive. A reboot and second attempt may work.

Are the older Warys going to be much different ? 431 works fine on the Tablet.

I see the Fujitsu has the same specs as the Gateway.
Maybe a wep problem.
Hardly worth the bother to use wep; wpa is extremely more secure.

Frank Cox wrote:

Béèm wrote:Frank Cox, mostly the back-light function is controlled by buttons as you say, or in the BIOS.
I don't think Wary 5.0 has code to do this.

My tablet has a button I always use for the brightness on the LCD frame. It works in every distro I have ever tried , windows, numerous Ubuntu derivatives, lucid , 4.2 . 431 and others I have forgotten but not in Wary so I doubt it has anything to do with the bios, that would affect the others as well. There is certainly the possibility I am wrong but it seems it has to be a bug in Wary, fortunately it is not a big problem .

Fortunately there is a second method of adjusting the brightness, FN F8 and when I remembered that and tried it it worked .


Thanks anyway

Any ideas on the wireless?

Well in that case Wary seems to do a funny thing then. Only Barry can tell.

In order to benefit from auto-upgrade and also if a puppy doesn't have SeaMonkey, I installed it outside the save file, in fact in /mnt/home/applications/seamonkey.
I created a desktop file and copy it to /usr/share/applications and run fixmenus.

In every puppy, except Wary, I can run this SeaMonkey from the menu.
When I type in a terminal, in /mnt/home/applications/seamonkey, my seamonkey starts.

Why do I have this issue in Wary?The name of the desktop file is SeaMonkey2-web-browser.desktop

Hi, Barry. Welcome back home and a happy new year.

Does the alsaconf calls depmod?

# diff alsaconf.old alsaconf

Adding a small sleep after touching the flag makes stable sound detection for me.
Wary-500j02 on HP Compaq nc4010

/etc/rc.d/rc.services, line 22-23

[ $GOODFLAG -eq 1 ] && touch /tmp/rc_d_rc_services_alsa_ok #read by /usr/sbin/delayedrun,
sleep 1

EDIT: 10 Jan 2010
The problem was not there.
Making sleep in /etc/init.d/10alsa was effective.
Insert sleep under the line 15, after all modprobe:

modprobe snd-mixer-oss
modprobe snd-seq-oss
modprobe snd-pcm-oss
for I in $(seq 4); do
[ -c /dev/mixer ] && break
sleep 1
done

@Barry,
I have managed to compile the latest svn source of ffmpeg
and libvpx. I am not sure how to test these thoroughly.
I tried ffplay on a variety of formats (mpeg, .avi DivX, etc) and managed
to see the movies with sound. I got some alsa pcm underrun messages
on the console, but there seemed to be no problems with the movie.
What other formats should be tested?
How do I test the rest of ffmpeg?
(I am not even sure about what it is supposed to do.)
How do I test libvpx?

I am afraid I hardly know anything about multimedia stuff.
Any pointers from anyone are welcome.

I am not certain about mmx support in vortex86Mx but I went ahead
and configured with --enable-mmx anyway. If problems come up I'll
try changing the config.

For the ffmpeg configuration the --enable-libfaad option apparently
no longer exists since it is not needed, according to some discussion
on the ffmpeg-dev forum.

-pskin

Shep,
I simply mounted the Wary 5.0 iso and copied the initrd.gz, vmlinuz and wary_500.sfs to my wary104 directory (renamed the corresponding old files so they wouldn't run), and ran it. It automatically updated beautifully from my old warysave.3fs file.
BS

Hello,

this Puppylinux Version cannot find my Soundcard (ES1978 or ES1968 / Maestro).

With Lupu 5.1.7 the same, but when I run alsaconf in a console from tty2 it finds it.

Please help me with what to do, as I cannot run alsaconf in a shell anymore.

Thank you!

rjbrewer wrote:
I have the same wireless card and don't have problems; not likely
to be a kernel issue.

Try a 098 or earlier wary; the extended pcmcia and usb module
loading may have something to do with it; a wild guess.

Sometimes it may switch interfaces if more than one install is on
the drive. A reboot and second attempt may work.

I have no problems in 431 and I have rebooted and tried many times.
I can connect with no security in Wary. What can I do to fix the problem if it is the pcmia loading or usb module?

This is a frugal install so I will try moving the install to a separate partition .

Thanks

Frank Cox, did you follow the advise of rcrsn51 and enter the pass-frase preceded by s:?
What network device do you get for the pcmcia card and which for the USB device?

Béèm wrote:Frank Cox, did you follow the advise of rcrsn51 and enter the pass-frase preceded by s:?
What network device do you get for the pcmcia card and which for the USB device?

]

Yes I tried putting an s before the passphrase. Not sure what you mean by the network devices.
The only thing I find to do with the wireless is :

Description: Intel Corporation Pro/Wireless 2200BG Network Connection
Vendor: 8086 Device: 4220 Kernel Module: ipw2200