Flash858,
Goto Menu->Desktop->Change Desktop
---
Hokal - I'll be recompiling the kernel again today or tomorrow. When I do, I'll build your drivers.
Puppeee 4.3X
jemimah,
Yea fbpanel on the left side does seem pretty buggy. I never actually tried it, but I can see that it probably isn't what I was looking for. I played around with the different panels from the matchbox project. The original worked ok but lacks a few features, the second version is better but is no longer developed and has zero documentation. I checked out the rox panel (that I never knew existed) and it looks quite nice. It even autohides! I'm really excited for the next puppeee release.
Yea fbpanel on the left side does seem pretty buggy. I never actually tried it, but I can see that it probably isn't what I was looking for. I played around with the different panels from the matchbox project. The original worked ok but lacks a few features, the second version is better but is no longer developed and has zero documentation. I checked out the rox panel (that I never knew existed) and it looks quite nice. It even autohides! I'm really excited for the next puppeee release.
-
dougeeebear
- Posts: 170
- Joined: Wed 08 Apr 2009, 15:36
- Location: Mid-South, USA
Back to my sound issue.
I have a full install of Puppeee dual-booting with Windows.
Scenario one:
I am in Windows, select Restart, select Puppeee in Grub.
No sound.
Reboot back into Puppeee and sound works.
Scenario two:
I am in Windows, select Turn Off.
Turn back on with power button, select Puppeee in Grub.
Sound works first time.
Scenario one is reproducible every time.
I'm sort of guessing Windows doesn't do a complete shut down on a reboot.
Is there a way to force the sound to work the first time in scenario one?
I have a full install of Puppeee dual-booting with Windows.
Scenario one:
I am in Windows, select Restart, select Puppeee in Grub.
No sound.
Reboot back into Puppeee and sound works.
Scenario two:
I am in Windows, select Turn Off.
Turn back on with power button, select Puppeee in Grub.
Sound works first time.
Scenario one is reproducible every time.
I'm sort of guessing Windows doesn't do a complete shut down on a reboot.
Is there a way to force the sound to work the first time in scenario one?
RC1 has been posted!
- New Easy installer and boot menu
Added: Flite Speech Synthesizer, OpenBox Window Manager, Nall Monitoring Applet, GtkSplitter, WavBreaker, Fotoxx, NicoEdit, Pzchmview, dir2iso, stardict
Removed: EasyTag, XfBurn, RipperX
Upgraded: Goggles Music Manager, Chrome, 3G modem detection scripts (Thanks to a special effort by Rerwin!), ALSA sound drivers, Wallpapers and themes, Eee-control now has ultrabright button(Thanks to MU!)
Xvesa wizard should now allow 1366x768 on the 1101HA - let me know if it doesn't
Bluetooth dongles should now be immediately functional upon being plugged in
Dougeeebear I've had similar issues with my 1005HA (only mine has audible static that sounds scarily like a broken fan!) The only solution I know of is to completely turn it off and then power it back on. You can try the new version with the new ALSA and see if that helps, but I doubt it will solve that particular problem.dougeeebear wrote:Back to my sound issue.
I have a full install of Puppeee dual-booting with Windows.
Scenario one:
I am in Windows, select Restart, select Puppeee in Grub.
No sound.
Reboot back into Puppeee and sound works.
Scenario two:
I am in Windows, select Turn Off.
Turn back on with power button, select Puppeee in Grub.
Sound works first time.
Scenario one is reproducible every time.
I'm sort of guessing Windows doesn't do a complete shut down on a reboot.
Is there a way to force the sound to work the first time in scenario one?
-
aarf
ok celeron is downloading now. am/was hoping for a quirky base. and upgrades ofjemimah wrote:I've fixed the permission problem for the Celeron Download.
xdelta
pwidgets inclding (no fans in temperature, and a battery monitor that works)
highlight click bug
5 ball
e2fsprog
openssl.
Last edited by aarf on Wed 12 May 2010, 15:55, edited 2 times in total.
chrome updated?
Hey, thanks for including Openbox!! I hope it becomes the default for Puppeee. I've been using it on the previous 4.50332 beta you put out; and it is superior in form and function to jwm or icewm; it's clean, sharp, and quick.
Also, just a quick question: chrome was having trouble connecting to gmail "SSL error." I found here that there is an updated chrome that fixes this for linux (http://googlechromereleases.blogspot.co ... l-fix.html). Is this the chrome included in the new Puppeee?
Thanks for all you do. This thing is great!!
I'll test the latest as soon as it is downloaded.
--Tim
eeepc 1000he
Also, just a quick question: chrome was having trouble connecting to gmail "SSL error." I found here that there is an updated chrome that fixes this for linux (http://googlechromereleases.blogspot.co ... l-fix.html). Is this the chrome included in the new Puppeee?
Thanks for all you do. This thing is great!!
I'll test the latest as soon as it is downloaded.
--Tim
eeepc 1000he
Change Desktop
I don't have a menu entry for it unfortunately. Mine is frugal, so I will update to the RC and see if it helps...
jemimah--
Do I still need the z***.sfs driver collection? I didn't find it in the package.
Jake
EDIT: Never mind. I had a bad download. I found everything the second around...
Do I still need the z***.sfs driver collection? I didn't find it in the package.
Jake
EDIT: Never mind. I had a bad download. I found everything the second around...
Last edited by jakfish on Wed 12 May 2010, 17:03, edited 1 time in total.
-
dougeeebear
- Posts: 170
- Joined: Wed 08 Apr 2009, 15:36
- Location: Mid-South, USA
Here's a quick heads up if you want to install to an internal drive...
The files initrd.gz and vmlinuz have to be manually copied from the boot directory to the usb flash drive root where eee-460.sfs is located.
Otherwise the puppy installer asks for a cd or a directory to find the files.
Maybe you should add the copy commands to bootinst.
It took me a few minutes to figure that out.
The files initrd.gz and vmlinuz have to be manually copied from the boot directory to the usb flash drive root where eee-460.sfs is located.
Otherwise the puppy installer asks for a cd or a directory to find the files.
Maybe you should add the copy commands to bootinst.
It took me a few minutes to figure that out.
I tried to install the new RC to a USB stick but on reboot I get something along the lines of " no bootable image found"
Stick has the following files -boot folder,eee-460.sfs and ze460332.sfs. Boot folder contains syslinux, initrd.gz, vmlinuz,mt86p, and a couple of other items (which I am assuming are extraneous.)
Any thoughts? All the files etc look "right" to me.
Stick has the following files -boot folder,eee-460.sfs and ze460332.sfs. Boot folder contains syslinux, initrd.gz, vmlinuz,mt86p, and a couple of other items (which I am assuming are extraneous.)
Any thoughts? All the files etc look "right" to me.
Fixed. http://puppeee.com/files/Puppeee%20RC1/md5sumsaarf wrote:was expecting md5sums somewhere
-
aarf
copied files (see image) to /puppeeerc1 on internal SDcard and grub booted with
in /mnt/sda1/boot/grub/menu.lst as usual.
posted via wifi from puppeeerc1
Code: Select all
title puppeeerc1 on dna
root (hd1,0)
kernel /puppeeerc1/vmlinuz phome=puppeeerc1 psubdir=puppeeerc1 pfix=fsck
initrd /puppeeerc1/initrd.gz
posted via wifi from puppeeerc1
- Attachments
-
- peee.files.jpg
- (25.77 KiB) Downloaded 826 times
Edit: eee 900, frugal install, USB stick
I've given it a test ride and find things very snappy. You have to reboot/save pupsave several times to get the quick shutdown working properly.
Too, I crashed xorg several times when trying to change global font or switch to xvega (xvega works fine). But I was trying to do this without yet making a save file. Once I had save file, and with a reboot, I could not replicate the xorg crashes. So rule of thumb: perhaps before tinkering with xorg, get a save file in order first.
Yes, bluetooth dongle found without a reboot. I could actually browse files on my Nokia E90, and send things back and forth.
The dreaded "external monitor" error is back when attempting a lid suspend. You had advice for that, a change in some sh file. Could you refresh my memory?
I assume that you did not find ulis's Bubbles 1.0.2 to be an adequate (and IMHO, a much better) replacement for your Windows Bubbles.
CUPS works fine.
Wifi up and down without complaint.
Chrome, while still maddeningly unadjustable GUI-wise and font-wise, is very perky.
One important thing about power management. Your previous live-saving code for battery:
#! /bin/sh
echo 95 24 1 > /proc/eee/fsb
echo 90 24 1 > /proc/eee/fsb
echo 85 24 1 > /proc/eee/fsb
echo 80 24 1 > /proc/eee/fsb
echo 75 24 1 > /proc/eee/fsb
echo 70 24 1 > /proc/eee/fsb
echo 70 24 0 > /proc/eee/fsb
echo "FSB to 70MHz"
Does that final line (echo 70 24 0 > /proc/eee/fsb) work in this kernel? I remember you saying it didn't work with one kernel, but don't know if it's this one.
Jake
I've given it a test ride and find things very snappy. You have to reboot/save pupsave several times to get the quick shutdown working properly.
Too, I crashed xorg several times when trying to change global font or switch to xvega (xvega works fine). But I was trying to do this without yet making a save file. Once I had save file, and with a reboot, I could not replicate the xorg crashes. So rule of thumb: perhaps before tinkering with xorg, get a save file in order first.
Yes, bluetooth dongle found without a reboot. I could actually browse files on my Nokia E90, and send things back and forth.
The dreaded "external monitor" error is back when attempting a lid suspend. You had advice for that, a change in some sh file. Could you refresh my memory?
I assume that you did not find ulis's Bubbles 1.0.2 to be an adequate (and IMHO, a much better) replacement for your Windows Bubbles.
CUPS works fine.
Wifi up and down without complaint.
Chrome, while still maddeningly unadjustable GUI-wise and font-wise, is very perky.
One important thing about power management. Your previous live-saving code for battery:
#! /bin/sh
echo 95 24 1 > /proc/eee/fsb
echo 90 24 1 > /proc/eee/fsb
echo 85 24 1 > /proc/eee/fsb
echo 80 24 1 > /proc/eee/fsb
echo 75 24 1 > /proc/eee/fsb
echo 70 24 1 > /proc/eee/fsb
echo 70 24 0 > /proc/eee/fsb
echo "FSB to 70MHz"
Does that final line (echo 70 24 0 > /proc/eee/fsb) work in this kernel? I remember you saying it didn't work with one kernel, but don't know if it's this one.
Jake