This seems to be some sort of JWM bug. Double click on the title bar to maximize it, and it will go back to normal.BJF wrote:Jemimah: When I open a file with EPDFViewer it is truncated on the right side, and everything east of the zoom-out on the toolbar is cut off. That margin cannot be moved by click-and-drag or any other reasonable activity but if I F11 to full screen then F11 back, there is a full window (sorry) including the minimise and stop controls and the proper movable right margin just as nature intended.
Puppeee 4.3X
Re: EPDFViewer does odd thing on File Open.
I'm compiling the 2.6.33 kernel right now. Many new drivers and upgrades. Atom-specific compilation is now an option so I will have to make two kernels, one for atom and one for celeron. I think I might try a low latency kernel this time and see how it performs.
I went over the whole config again. I think I figured out why samba doesn't work so test it again when I release this kernel.
I also broke down and ebayed a 701SD. I was thinking about getting a 1201N as well but I think I'll wait until the price comes down. There's hasn't been a lot of clamoring around here for support for the 11 and 12inch eees. Perhaps they perform fast enough that there's little demand for ultralight OSes for them.
I went over the whole config again. I think I figured out why samba doesn't work so test it again when I release this kernel.
I also broke down and ebayed a 701SD. I was thinking about getting a 1201N as well but I think I'll wait until the price comes down. There's hasn't been a lot of clamoring around here for support for the 11 and 12inch eees. Perhaps they perform fast enough that there's little demand for ultralight OSes for them.
-
dougeeebear
- Posts: 170
- Joined: Wed 08 Apr 2009, 15:36
- Location: Mid-South, USA
I just now realised un-checking "Enable Bluetooth" in eee-control doesn't survive a reboot.
"Disable Bluetooth at Startup" is checked.
Puppeee beta 3.6 on 1000H.
Previous versions worked ok.
EDIT:
When I reboot into Windows, bluetooth is still enabled, so I don't think it actually gets disabled at all.
Disabling in Windows then booting into Puppeee it remains disabled (according to the tickbox).
Enable then disable via tickbox, then reboot back into Windows, it is enabled.
Very strange.
"Disable Bluetooth at Startup" is checked.
Puppeee beta 3.6 on 1000H.
Previous versions worked ok.
EDIT:
When I reboot into Windows, bluetooth is still enabled, so I don't think it actually gets disabled at all.
Disabling in Windows then booting into Puppeee it remains disabled (according to the tickbox).
Enable then disable via tickbox, then reboot back into Windows, it is enabled.
Very strange.
-
dougeeebear
- Posts: 170
- Joined: Wed 08 Apr 2009, 15:36
- Location: Mid-South, USA
installing firefox
I installed Firefox 2.0.0.7 using Puppy Package Manager. Installation went fine except when it informed me of dependencies, the window was too short for the list and could not be scrolled. I tried minimize/maximize and then all the text was gone.
Well, since it apparently just wanted to inform that all dependencies were fulfilled, I simply hit return, and it ended fine, with Firefox installed.
When I tried to start Firefox from the menu, it started Chrome. When I started terminal, wrote Firefox and hit return, it started Chrome. Only when I typed the whole path, did Firefox start.
I changed /usr/local/bin/defaultbrowser from Chrome to Firefox and now it works correctly. From menu when Firefox is clicked, Firefox gets to run and when Chrome is clicked, Chrome runs. Also desktop Browse button starts Firefox.
Should I have changed something else? FF as default browser is fine for me, but does it affect something else?
Forgot to say that I am using Puppeee 4.35 beta 3.6 on eeePc 900.
Well, since it apparently just wanted to inform that all dependencies were fulfilled, I simply hit return, and it ended fine, with Firefox installed.
When I tried to start Firefox from the menu, it started Chrome. When I started terminal, wrote Firefox and hit return, it started Chrome. Only when I typed the whole path, did Firefox start.
I changed /usr/local/bin/defaultbrowser from Chrome to Firefox and now it works correctly. From menu when Firefox is clicked, Firefox gets to run and when Chrome is clicked, Chrome runs. Also desktop Browse button starts Firefox.
Should I have changed something else? FF as default browser is fine for me, but does it affect something else?
Forgot to say that I am using Puppeee 4.35 beta 3.6 on eeePc 900.
Re: installing firefox
There's a symlink in /usr/local/bin/, firefox->defaultbrowser. This is a workaround because Abiword assumes firefox is installed. Just delete the symlink and everything should start to make sense.kjp wrote: Should I have changed something else? FF as default browser is fine for me, but does it affect something else?
-
dougeeebear
- Posts: 170
- Joined: Wed 08 Apr 2009, 15:36
- Location: Mid-South, USA
Firefox
jemimah wrote:
. I deleted that symlink and restored defaultbrowser and then Chrome worked. Unfortunately, FF didn't start from the menu anymore 
. I added a symlink to /opt/mozilla.org/bin/firefox<-firefox, and it started to work again. Strange, since /opt/mozilla.org/bin is in the path.
But I'll probably change default browser into Firefox again and see if it causes problems. This system is going to a friend for few months and she's used Firefox. So now I can point to Browse button and tell her to push that to get into net. Hmm, need to check the Flash too...
Thanks! Makes much more senseThere's a symlink in /usr/local/bin/, firefox->defaultbrowser. This is a workaround because Abiword assumes firefox is installed. Just delete the symlink and everything should start to make sense.
. I deleted that symlink and restored defaultbrowser and then Chrome worked. Unfortunately, FF didn't start from the menu anymore . I added a symlink to /opt/mozilla.org/bin/firefox<-firefox, and it started to work again. Strange, since /opt/mozilla.org/bin is in the path.But I'll probably change default browser into Firefox again and see if it causes problems. This system is going to a friend for few months and she's used Firefox. So now I can point to Browse button and tell her to push that to get into net. Hmm, need to check the Flash too...
Beta-3.6
I set up modules with r8192se_pci having preference over rtl8187se, then connected to wireless and wifi-driver indicated rtl8187se.
Next I rmmod rtl8187se and no wireless connection. So if I did things correctly the rtl8192se may not support the 701SD. I see you bought a 701SD wish I knew more, am reading up a little on bash scripting.
Next I rmmod rtl8187se and no wireless connection. So if I did things correctly the rtl8192se may not support the 701SD. I see you bought a 701SD wish I knew more, am reading up a little on bash scripting.
gerry, that's very odd. I really don't know what the problem might be.
mfalls - yeah I don't think the rtl8192 driver would work. But it was worth a shot. I took a look at the source code for the new version of rtl8187se, but no mention of rfkill in the source, so I think it's not fixed, but I could be wrong.
The good news is the new kernel is faster, and I figured out how to make the init script run faster without sacrificing reliablity. It really flies after it boots too (at least the atom version I'm testing now).
The new rt2800pci driver doesn't seem to work well, so I'm going to stick with rt2860sta, which now supposedly supports the rt3090 card too.
The bug where the wifi won't come back on after rebooting if it's off when you shutdown is still there (ath9k/ath5k).
mfalls - yeah I don't think the rtl8192 driver would work. But it was worth a shot. I took a look at the source code for the new version of rtl8187se, but no mention of rfkill in the source, so I think it's not fixed, but I could be wrong.
The good news is the new kernel is faster, and I figured out how to make the init script run faster without sacrificing reliablity. It really flies after it boots too (at least the atom version I'm testing now).
The new rt2800pci driver doesn't seem to work well, so I'm going to stick with rt2860sta, which now supposedly supports the rt3090 card too.
The bug where the wifi won't come back on after rebooting if it's off when you shutdown is still there (ath9k/ath5k).
ref. BT headset / speaker.
jemimah,
unfortunately no success with your BT instructions. I can hear the speaker producing klicking sound, so it is controlled, but when I play a song I get this:
aqualung --device bluetooth
and when I start the mp3 song I get this:
ALSA lib audio/pcm_bluetooth.c
(audioservice_expect) BT_START_STREAM failed
ALSA lib audio/pcm_bluetooth.c
(audioservice:recv) Too short (1byte) IPC
And I get this message in a loop again and again!!
I was so excited when you announced that it works
With Beta6 I found a small bug with the sd card reader of my 901. When I boot the 901 with inserted sd card it will mount the card
with that green mark on the icon. If I mouseclick the card icon, the pmount puppy drive mounter shows up and my sd card icon disappears. After reinserting the sd card everything works fine.
I'm already curious on the Beta7
jemimah,
unfortunately no success with your BT instructions. I can hear the speaker producing klicking sound, so it is controlled, but when I play a song I get this:
aqualung --device bluetooth
and when I start the mp3 song I get this:
ALSA lib audio/pcm_bluetooth.c
(audioservice_expect) BT_START_STREAM failedALSA lib audio/pcm_bluetooth.c
(audioservice:recv) Too short (1byte) IPCAnd I get this message in a loop again and again!!
I was so excited when you announced that it works
With Beta6 I found a small bug with the sd card reader of my 901. When I boot the 901 with inserted sd card it will mount the card
with that green mark on the icon. If I mouseclick the card icon, the pmount puppy drive mounter shows up and my sd card icon disappears. After reinserting the sd card everything works fine.
I'm already curious on the Beta7