Fluppy 013
about 3 hrs surfing. getting some short freezes in opera 10.60 which had mostly disappeared in peee-rc5. on one long freeze tried to kill opera and it then needed ctrl+alt+backspace to proceed. last fsck was all clean after restart X. wifi holding superbly. haven't test other things. fsck on opera's partition still clean.
Hi jemimah,
Testing 003 on a HP laptop centrino duo with a full install
First tried upgrading 002 (which was working fine).
problem - all the desktop icons disappeared ? except the drive icons.
everything else seemed to work fine
I did make the 003 ISO myself from 002 ISO so that could have caused it
reinstalled 003 (full) completely all seems to be working fine.
One very good point for me. I have a 20" screen plugged in to my laptop
When watching BBC iplayer I can now have full screen video (1680x1050)
this works in chrome and opera
In other puppies when I switch to full screen I get a window top left showing the laptop screen resolution (1024x768) and the rest of the 20" screen freezes.
It would be nice to know why your build works and other puppies don't.
thanks
DC
Testing 003 on a HP laptop centrino duo with a full install
First tried upgrading 002 (which was working fine).
problem - all the desktop icons disappeared ? except the drive icons.
everything else seemed to work fine
I did make the 003 ISO myself from 002 ISO so that could have caused it
reinstalled 003 (full) completely all seems to be working fine.
One very good point for me. I have a 20" screen plugged in to my laptop
When watching BBC iplayer I can now have full screen video (1680x1050)
this works in chrome and opera
In other puppies when I switch to full screen I get a window top left showing the laptop screen resolution (1024x768) and the rest of the 20" screen freezes.
It would be nice to know why your build works and other puppies don't.
thanks
DC
I switched the icon theme since the last version. If anyone else gets the icon problem with upgrades, just use the Rox Icon Switcher to switch the theme and the icons will be fixed.
If your full screen video works in Quirky you can probably blame your freeze on Xorg 7.3 or the old kernel. Otherwise I haven't the foggiest idea what the difference could be - maybe installing Xorg-Full in other Puppies will fix it.
If your full screen video works in Quirky you can probably blame your freeze on Xorg 7.3 or the old kernel. Otherwise I haven't the foggiest idea what the difference could be - maybe installing Xorg-Full in other Puppies will fix it.
Holy crap!!!
This is the first new kernel Puppy version that lets me
install and run Ttuuxxxs vlc lite 8.6.
Gxine is almost as good.
No overheating problems.
Jemimah; this is just great on my 12" Inspiron 700m, using
vesa at 1024 x 768.
edit;
Full install to hard drive was a piece of cake too.
This is the first new kernel Puppy version that lets me
install and run Ttuuxxxs vlc lite 8.6.
Gxine is almost as good.
No overheating problems.
Jemimah; this is just great on my 12" Inspiron 700m, using
vesa at 1024 x 768.
edit;
Full install to hard drive was a piece of cake too.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Comparing Gxine to this Vlc using Htop, playing mp4 videojemimah wrote:Do you have a link for "vlc light"? I am wondering how small it is. Maybe it could fit in the sfs.
Edit: Nevermind, found it. 8MB, a bit too large...
almost full screen.
Gixine 60% + cpu
Vlc 40% + cpu
Gxine 80/993 ram
Vlc 64/993 ram
The new gnome-mplayer and mplayer versions are a
complete disaster with my favorite dvds.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
I've never eliminated Gxine on the earlier installs either.jemimah wrote:I'd consider replacing Gxine, but both Goggles and Xfmedia need Xine.
It's just nice to be able to have the Vlc .pet option.
Edit;
Google Chrome don't play nice with Vlc or mms video streams;
dumped it and installed Seamonkey 1.1.18.
Last edited by rjbrewer on Thu 17 Jun 2010, 07:01, edited 1 time in total.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
I have been experimenting with the Fluppy 002 vesa (Xvesa) driver and my Acer Aspire Revo that has Nvidia Ion chipset. I have found that using the standard Xvesa resolution 1280 by 1024 looks fairly good on my 1366 by 768 monitor. The monitor does automatically adapt and display the resolution. The start up takes a while.
I did some research on Xvesa. There is a tool called Xvesa that provides information (needed to run at console prompt without Xserver running) on the available modes. Specifically, there is the command Xvesa -force -listmodes that shows all the video modes in BIOS list. Puppy and Fluppy do not have the Xvesa tool. Does anyone know how to get a list of the video modes from the BIOS? Thanks in advance for any help.
I did some research on Xvesa. There is a tool called Xvesa that provides information (needed to run at console prompt without Xserver running) on the available modes. Specifically, there is the command Xvesa -force -listmodes that shows all the video modes in BIOS list. Puppy and Fluppy do not have the Xvesa tool. Does anyone know how to get a list of the video modes from the BIOS? Thanks in advance for any help.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Yes, xvesa in Fluppy does show the "standard" vesa modes. I kept trying the listed modes until I found the highest resolution that work and looked good.
I was hoping to find all modes including the non-standard ones that might be in BIOS. It might be possible to get 1366 by 768 mode (if present) used by many laptops. I will keep looking! Thank you for the reply
I was hoping to find all modes including the non-standard ones that might be in BIOS. It might be possible to get 1366 by 768 mode (if present) used by many laptops. I will keep looking! Thank you for the reply
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
jemimah,
Just now got to a Windows machine to test Fluppy003 -- bootinst.sh didn't work for my thumbdrive (using Linux).
I am not seeing any wireless access points... oh wait... I think I see why. If you look at the b43 folder now located in /lib/firmware/, you will notice that the next level down in that b43 directory is a directory named 'lib' -- and inside that directory is a directory called 'firmware' -- and inside that directory is the base b43 directory. So the base directory located at /lib/firmware/b43/lib/firmware/b43 really should be /lib/firmware/b43. Might also need the tar.gz in /lib/modules/all-firmware to function, although this is a personal gut feeling rather than a firm statement ATM. Does the b43.tar.gz have to be in /lib/modules/all-firmware to register or something? I seem to recall an issue with an earlier kernel where the tar.gz was supposed to automatically extract from /lib/modules/all-firmware to /lib/firmware/ .... or something to that effect. Maybe I don't know enough about it.
The good news is that creating a 128MB save file on the thumbdrive did not wipe out the ability to reboot this time around.
Let me play with this a bit longer....
-Roy
EDIT: dmesg is still telling me
All of the above is with a Dell Mini-9 and stock broadcom 4312 wireless card.
Just now got to a Windows machine to test Fluppy003 -- bootinst.sh didn't work for my thumbdrive (using Linux).
I am not seeing any wireless access points... oh wait... I think I see why. If you look at the b43 folder now located in /lib/firmware/, you will notice that the next level down in that b43 directory is a directory named 'lib' -- and inside that directory is a directory called 'firmware' -- and inside that directory is the base b43 directory. So the base directory located at /lib/firmware/b43/lib/firmware/b43 really should be /lib/firmware/b43. Might also need the tar.gz in /lib/modules/all-firmware to function, although this is a personal gut feeling rather than a firm statement ATM. Does the b43.tar.gz have to be in /lib/modules/all-firmware to register or something? I seem to recall an issue with an earlier kernel where the tar.gz was supposed to automatically extract from /lib/modules/all-firmware to /lib/firmware/ .... or something to that effect. Maybe I don't know enough about it.
The good news is that creating a 128MB save file on the thumbdrive did not wipe out the ability to reboot this time around.
Let me play with this a bit longer....
-Roy
EDIT: dmesg is still telling me
Code: Select all
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
#
re:- full screen video, 20" screen plugged into laptop
fluppy 003 vs lucid 204 ( and other 431 puppies)
fluppy 003 xorgwizard screen lists all resolutions.
lucid 204 xorgwizard screen lists the laptop resolution with the option of more which then lists all resolutions.
also affects windows zooming to full screen. they only zoom to laptop resolution and top left of screen.
It seems to be in the initial detection of the screen or available choices. Problem is trying to automatically choose screen resolutions for new uses vs possible resolutions available.
Is the fluppy way easy to transfer to other puppies?
DC
fluppy 003 vs lucid 204 ( and other 431 puppies)
fluppy 003 xorgwizard screen lists all resolutions.
lucid 204 xorgwizard screen lists the laptop resolution with the option of more which then lists all resolutions.
also affects windows zooming to full screen. they only zoom to laptop resolution and top left of screen.
It seems to be in the initial detection of the screen or available choices. Problem is trying to automatically choose screen resolutions for new uses vs possible resolutions available.
Is the fluppy way easy to transfer to other puppies?
DC
I didn't recompile the module yet. But what's odd is that it supposedly works on Quirky with the current configuration. I'll probably have a go at compiling the wl module.Roy wrote:
EDIT: dmesg is still telling meCode: Select all
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000 b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead. b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration. #