@pemasu: If I use "pdev1=sdb1" AND Puppy can find the sfs file on a hard drive, it will use that one instead. But if the only sfs file is on the flash drive, Puppy will eventually find it. However, "pdev1=pemasu" works too!
So in snail's situation, it sounds like you have to give Puppy the WRONG arguments. That forces the init to search elsewhere, which gives the flash drive enough time to wake up and be detected.
So maybe the older Puppies work for him because their USB detection works slower.
Lucid Puppy 5.2.7 RC2
@pemasu: It sounds like the best work-around is to use NO options.
Puppy will eventually find the flash drive anyway, and the drive is more likely to be ready.
FWIW, TInyCore Linux has a "waitusb=n" option. This supposedly pauses the init until a flash drive is ready.
Code: Select all
default vmlinuz initrd=initrd.gzFWIW, TInyCore Linux has a "waitusb=n" option. This supposedly pauses the init until a flash drive is ready.
We are not using the Ubuntu kernel, which the article applies to. Our kernel 2.6.33.2 was compiled by 01micko. Thanks.Not sure how this affects the current 52X but since this puppy is based on Ubuntu, it's something developers might want to look into!
========================================================================
Ubuntu Security Notice USN-1168-1 July 15, 2011 linux vulnerabilities ========================================================================
http://lwn.net/Articles/451809/
Last edited by playdayz on Sun 17 Jul 2011, 16:22, edited 1 time in total.
Sorry snail, but please use luci-265. That is the one with all of the fixes properly in place.Neither the "fixed" 525 nor 264 can make a bootable USB stick on either my laptop nor my desktop
With luci-265, I just used bootflash to make a bootable usb stick, which booted on a machine with no drives connected, as well as my regular machine.
I also used gparted to make an ext4 formatted usb stick and used Puppy Universal Installer to install luci-265. That also booted on both machines.
---------------------------------------------------------------------------------------------------
rcrsn51, FYI, We are not using the new Woof builds. We are using the same Woof as Lucid 5.2.5. It's a bit of a story, but after the Woof we used to build 5.2.5, Barry made some changes and replaced many of the hardware detection and config scripts with new scripts of his own. Those new scripts of Barry's were called the "zzz-scripts" so Lucid 5.2.5 was "the last non-zzz" Puppy. There were big changes in those zzz scripts and IMHO it is better to let Lucid remain the last non-zzz Puppy. Barry probably disagrees but again IMHO using the new scripts would be tantamount to starting a new distro--which I discussed above in the case of a new kernel--if you are going to do it you may as well go all the way and start from scratch. Fortunately, rerwin, who was one of the main developers of the non-zzz scripts is helping considerably with Lucid 5.2.6. He had been developing and testing improvements for several months with the modem-modprobe enhancements, which are now all incorporated into luci-265, in addition to some other things he has found. My final opinion of the morningBarryK recently made changes to USB detection and these would now appear in all new woof builds.
is that it might be a good thing to have two different lines of development.http://www.murga-linux.com/puppy/viewto ... 71&t=57290
--------------------------------------------------------------------------------------------
James C, Did that nasty Nvidia 8400 work correctly with Lucid 5.2.5?
-----------------------------------------------------------------------------------------------
jim3560, That's good news. It didn't connect with luci-264 but it did with luci 265, am I right?265 manual frugal install to ext4. used the usual broadcom wl pet and configured wifi with the connection wizard, rebooted made save file expecting to need Frisbee to made actual wifi connection and behold when booted up it was connected to my surprise.
Last edited by playdayz on Sun 17 Jul 2011, 16:41, edited 1 time in total.
i915 modeset update
playdayz,
After working with JonT on his intel i915-type graphic card black screen problem, and having done some googling, I have concluded that it would be wise to, instead of forcing modeset 0 for cards that cannot handle "1", that not setting a mode, at all, is more conservative and may help in more situations.
JonT's case is not fixed by modeset 0. When I change the i915 rule and conf file to omit the modeset argument when installing for the problematic cards (such as mine), my screen works as well as it does with modeset 0. It might help JonT, as well, but I must wait until he can test it.
Anyway, I attach the update to the modeset files and hope those with the troublesome graphics card will try it. It supports 2 versions of the "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562]" card. Anyone with another version of the card -- or any card using the i915 module -- who experiences the black-screen problem needs to report that here (or by PM to me) and (1) copy the relevant entry from pupscan and (2) attach the file /tmp/udevtrace.log, so I can determine the subvendor/device IDs. Then I can add a rule for that case.
Thanks for any feedback on this.
Richard
UPDATE: This is superceded by a flexible version on the next page. It defaults to using mode 0, but let's users modify a rules file to try using no modeset argument. But "update-1" makes it easy to try omitting the modeset, in case that works better than mode 0.
After working with JonT on his intel i915-type graphic card black screen problem, and having done some googling, I have concluded that it would be wise to, instead of forcing modeset 0 for cards that cannot handle "1", that not setting a mode, at all, is more conservative and may help in more situations.
JonT's case is not fixed by modeset 0. When I change the i915 rule and conf file to omit the modeset argument when installing for the problematic cards (such as mine), my screen works as well as it does with modeset 0. It might help JonT, as well, but I must wait until he can test it.
Anyway, I attach the update to the modeset files and hope those with the troublesome graphics card will try it. It supports 2 versions of the "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562]" card. Anyone with another version of the card -- or any card using the i915 module -- who experiences the black-screen problem needs to report that here (or by PM to me) and (1) copy the relevant entry from pupscan and (2) attach the file /tmp/udevtrace.log, so I can determine the subvendor/device IDs. Then I can add a rule for that case.
Thanks for any feedback on this.
Richard
UPDATE: This is superceded by a flexible version on the next page. It defaults to using mode 0, but let's users modify a rules file to try using no modeset argument. But "update-1" makes it easy to try omitting the modeset, in case that works better than mode 0.
- Attachments
-
- i915_update-1.pet
- changes modeset0 to no modeset argument to i915 module.
- (3.18 KiB) Downloaded 230 times
Last edited by rerwin on Mon 18 Jul 2011, 03:36, edited 1 time in total.
-
Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Installed the usual Lin'N'Win FRUGAL of 265
When clicking on the network icon in the tray, /var/cache/fontconfig it started to fill. I could stop it by restarting X otherwise this would have continued as in the 263.
Fontconfig contains:Really annoying
When clicking on the network icon in the tray, /var/cache/fontconfig it started to fill. I could stop it by restarting X otherwise this would have continued as in the 263.
Fontconfig contains:
Code: Select all
sh-4.1# ls -l -h
total 17M
-rw-r--r-- 1 root root 0 2011-07-14 20:03 01cd275fb48ce64cbfd43fad75f70f84-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 200 2011-07-11 01:35 0251a5afa6ac727a1e32b7d4d4aa7cf0-le32d4.cache-3
-rw-r--r-- 1 root root 625K 2011-07-14 19:49 02ee123a0860abc6ceda00dd4ed59b79-le32d4.cache-3
-rw-r--r-- 1 root root 648K 2011-07-14 19:50 0df8fe5d02ee8583138c6b7763cd324c-le32d4.cache-3
-rw-r--r-- 1 root root 400K 2011-07-14 19:50 0df8fe5d02ee8583138c6b7763cd324c-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:02 14fa5e9b6e4346b7866fe778850f1a0c-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:03 150693aab1ff8eca48c4d70129ca9b03-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 626K 2011-07-14 19:49 3218fa3b4172593e560d87ddf0575d54-le32d4.cache-3
-rw-r--r-- 1 root root 638K 2011-07-14 19:49 33c90b7357914c56654ec09e1f66de6c-le32d4.cache-3
-rw-r--r-- 1 root root 642K 2011-07-14 19:49 35d0c1327dead03c15c9e8a765e8b535-le32d4.cache-3
-rw-r--r-- 1 root root 633K 2011-07-14 19:49 37730d1c1015ce466a08daa08a47462c-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:02 3827ca61fdd2dec154dc063b0d87477c-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 636K 2011-07-14 19:49 40b6ffe248ac2e78d9f92d2b103c323c-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 19:50 44a90c20b9d2d80fcb35e18386e91e4d-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 644K 2011-07-14 19:50 48fad9be8bb80a9bb24bd1dd78a57449-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:02 4be6828ca14ddeefc620312f814c50f7-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 640K 2011-07-14 19:49 4e31350b1ab51c34530117e2e748e1fe-le32d4.cache-3
-rw-r--r-- 1 root root 634K 2011-07-14 19:49 534e9043cc3cc35d163531a332ad1028-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 19:50 53abcefd36b5363585d4890bebc3116a-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 640K 2011-07-14 19:49 548cd286caa70b9bf8037e59a170b035-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:03 562d13a8ed22517ee6ea33243a4a6484-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:02 5c62166b8870d1ed6a9452a736160db8-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:03 5d5930eb1c14c39cafcc0d208bae409e-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 645K 2011-07-14 19:50 60d45a244d97b9a5649c514608c0508a-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:02 6641b9d389c04093f7ec9cfd9edd2ad3-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 19:50 6794f1786ac2d96d89e3955febf86cd0-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:03 6864d5485a904fd92e1d0fb0a988d132-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 625K 2011-07-14 19:49 8b2b1a1f2918423753eaece9c81c7611-le32d4.cache-3
-rw-r--r-- 1 root root 644K 2011-07-14 19:50 8fa0d53264866d1371eda3fcba08a528-le32d4.cache-3
-rw-r--r-- 1 root root 629K 2011-07-14 19:49 9a0a7efd050bc08029b30b81663e9b5f-le32d4.cache-3
-rw-r--r-- 1 root root 5,3K 2011-07-11 01:35 a0fc735e35b02c1c3c93fdfc0b90a089-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:02 a4300b3aa05aeab4d87fae1559c8f9ba-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 642K 2011-07-14 19:50 ad2c42a7c4192c8b54d0d29d622a350a-le32d4.cache-3
-rw-r--r-- 1 root root 633K 2011-07-14 19:49 b071f8dffad03d386b01a06a489fd372-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:03 b1646d717c9a87304ad5b9c4994b66d4-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 630K 2011-07-14 19:49 b432ec6c64d32e6967aedc82d6696c19-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:02 b55bf12d9fad5b335421e25f05231415-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 626K 2011-07-14 19:49 bb4d715c5d2b0d0e3a3d3167fd6211b5-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 19:50 bf83a611e87e743267f0e458907c6519-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 645K 2011-07-14 19:50 c176b2a97610e63917192422c2bd7ad7-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:03 cbcf07c061407cb7ed86af0ce3c4834d-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 629K 2011-07-14 19:49 ccf06f84dfe5cb364f3dabf64ad76a3e-le32d4.cache-3
-rw-r--r-- 1 root root 623K 2011-07-14 19:49 d04038e664b0033ae700a78c51f179d3-le32d4.cache-3
-rw-r--r-- 1 root root 634K 2011-07-14 19:49 d0f0476681daea4610e38741e464c176-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:03 d60bc4363ba01a4c42b58a199f70d026-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:03 d93439c2cb6667788c66ab6d01104d65-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 0 2011-07-14 20:02 e29fddecc395e306952a3688499d9e45-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 638K 2011-07-14 19:49 e481755965d41e132dcfb9d07438a1d8-le32d4.cache-3
-rw-r--r-- 1 root root 636K 2011-07-14 19:49 ec0919ede73b236f8930a4c816927b7c-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:03 f03c0763ce8c912db35fdcb0ff9170c3-le32d4.cache-3.NEW
-rw-r--r-- 1 root root 630K 2011-07-14 19:49 f83626dfdd8e82860e8acf63233fe296-le32d4.cache-3
-rw-r--r-- 1 root root 0 2011-07-14 20:03 f9e117f3d9c05df7f4a2ddac4c6eef7e-le32d4.cache-3.NEW
sh-4.1# Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
USB Boot fails on EEE701with 264
It's NOT just my Compaqs!
I'll try 265 after breakfast.
I'll also try unhiding my sfs on the hard drive and seeing what happens.
I'll try 265 after breakfast.
I'll also try unhiding my sfs on the hard drive and seeing what happens.
minor pupscan update
playdayz,
While trying 265, I ran pupscan, only to find that it did not include the "kernel modules" for the PCI devices. It turns out that when pupscan uses lspci to get the info, lspci expects a "pcimap" to be available to it, but it was not present. There is a simple explanation and fix.
At bootup, the busybox version of depmod is run, to identify the modules present. But it does not create the various "maps". The maps are created by the "full" depmod function, which is run only as needed (such as by the ALSA wizard). Once something has run depmod, pupscan/lspci have their pcimap.
To fix this issue, I added a test for the map and, if absent, run depmod to create it. The resultant package is attached, for testing and replacement in luci.
Richard.
While trying 265, I ran pupscan, only to find that it did not include the "kernel modules" for the PCI devices. It turns out that when pupscan uses lspci to get the info, lspci expects a "pcimap" to be available to it, but it was not present. There is a simple explanation and fix.
At bootup, the busybox version of depmod is run, to identify the modules present. But it does not create the various "maps". The maps are created by the "full" depmod function, which is run only as needed (such as by the ALSA wizard). Once something has run depmod, pupscan/lspci have their pcimap.
To fix this issue, I added a test for the map and, if absent, run depmod to create it. The resultant package is attached, for testing and replacement in luci.
Richard.
- Attachments
-
- pupscan_fix-2.pet
- more resilient pupscan
- (4.25 KiB) Downloaded 207 times
Re: USB Boot fails on EEE701with 264
Then maybe it's your flash drive. Because what you are seeing is not a wide-spread problem.Snail wrote:It's NOT just my Compaqs!
Trying 265...
My Intel D510MO boots. Yay!
That confirms both the no hard drive problem and the isolinux problems are fixed.
I booted on the laptop, created a bootable flash drive and booted the D510MO off the flash drive, confirming Universal Installer works for me.
Aesthetically, can't say I like the default look. But hey, who cares, I can get my Blue Moon icons back.
Menu bug appears gone also.
Internet connection worked.
My graphics on the D510MO were pretty snappy compared to Lupu511 but at least part of that is using a 1440x900 monitor rather than a 1920x1220 (I think) one. Particularly for displaying long pages. However if I set the background plain grey, and move the cursor around, I get a weird effect on the background. Needs a little more investigation.
The one bug I definitely did detect was the same old one that has always been here, you can't "pfix=fsck" on a heavy-encrypted pupsave (not sure about lite-encrypted). This has never worked ever since we got "pfix=fsck". It should be an easy fix in initrd.gz:
modprobe cryptoloop
modprobe aes
losetup-FULL -e aes /dev/loop6 xyz (where xyz is the name of the pupsave)
e2fsck -y /dev/loop6
(Note correction in bold.)
At least that's the way I do it. Maybe need to see if loop6 is available first.
This is particularly annoying since with encryption, it is at least theoretically safer to use ext2 in the pupsave rather than ext3, and ext2 really needs to be fsck'ed every so often.
My Intel D510MO boots. Yay!
That confirms both the no hard drive problem and the isolinux problems are fixed.
I booted on the laptop, created a bootable flash drive and booted the D510MO off the flash drive, confirming Universal Installer works for me.
Aesthetically, can't say I like the default look. But hey, who cares, I can get my Blue Moon icons back.
Menu bug appears gone also.
Internet connection worked.
My graphics on the D510MO were pretty snappy compared to Lupu511 but at least part of that is using a 1440x900 monitor rather than a 1920x1220 (I think) one. Particularly for displaying long pages. However if I set the background plain grey, and move the cursor around, I get a weird effect on the background. Needs a little more investigation.
The one bug I definitely did detect was the same old one that has always been here, you can't "pfix=fsck" on a heavy-encrypted pupsave (not sure about lite-encrypted). This has never worked ever since we got "pfix=fsck". It should be an easy fix in initrd.gz:
modprobe cryptoloop
modprobe aes
losetup-FULL -e aes /dev/loop6 xyz (where xyz is the name of the pupsave)
e2fsck -y /dev/loop6
(Note correction in bold.)
At least that's the way I do it. Maybe need to see if loop6 is available first.
This is particularly annoying since with encryption, it is at least theoretically safer to use ext2 in the pupsave rather than ext3, and ext2 really needs to be fsck'ed every so often.
Last edited by PaulBx1 on Mon 18 Jul 2011, 01:11, edited 1 time in total.
USB Boot - 265 WORKS!
Just did a bootflash with 265. The standard syslinux.cfg now works on both Compaqs and the EEE.
Sorry to waste everybody's time but both 525 with Bigpup's fix and 264 were advertised as having working bootflash and they didn't. I initially missed the 265 upgrade due to testing this issue. As I initially suspected a user error, it darn near did my head in trying to find what I did wrong. It was purely by chance that I found Pemasu's thread on IcePuppy, which alluded to it being a general problem.
@rcrsn51
I did of course test with two usb sticks before posting. It is one of those that has just worked with 265. Both sticks were reasonably new and little-used. Mucking around on this issue probably accounts to 90% of the writes to those sticks since new!
Some minor observations: The bootflash window can find an iso on /mnt/sda5/Puppy ISOs/ but if you select it, the process fails because it appears that ISOs cannot be mounted at that level down in the directory structure. The red error message panel about the failure loads underneath the yellow message strip about loading the files. The yellow strip is persistent, giving the impression that the bootflash is locked up. This doesn't appear to be the case after the OK button on the red panel is clicked but the yellow message still stays. A minor but confusing glitch. (A symlink in /mnt/sda/ is enough to allow mounting)
Wary 512 also has a limitation about mounting ISO's down the directory levels but it goes deeper than 265 from memory. What is supposed to work? Why should there be a limitation?
A wish-list item for the future: When you unmount a filesystem-in-a-file, would it be possible to clean up the "/root/ISOs+luci-265.iso" type of stuff that appears in Rox persistently unless specifically deleted?
Sorry to waste everybody's time but both 525 with Bigpup's fix and 264 were advertised as having working bootflash and they didn't. I initially missed the 265 upgrade due to testing this issue. As I initially suspected a user error, it darn near did my head in trying to find what I did wrong. It was purely by chance that I found Pemasu's thread on IcePuppy, which alluded to it being a general problem.
@rcrsn51
I did of course test with two usb sticks before posting. It is one of those that has just worked with 265. Both sticks were reasonably new and little-used. Mucking around on this issue probably accounts to 90% of the writes to those sticks since new!
Some minor observations: The bootflash window can find an iso on /mnt/sda5/Puppy ISOs/ but if you select it, the process fails because it appears that ISOs cannot be mounted at that level down in the directory structure. The red error message panel about the failure loads underneath the yellow message strip about loading the files. The yellow strip is persistent, giving the impression that the bootflash is locked up. This doesn't appear to be the case after the OK button on the red panel is clicked but the yellow message still stays. A minor but confusing glitch. (A symlink in /mnt/sda/ is enough to allow mounting)
Wary 512 also has a limitation about mounting ISO's down the directory levels but it goes deeper than 265 from memory. What is supposed to work? Why should there be a limitation?
A wish-list item for the future: When you unmount a filesystem-in-a-file, would it be possible to clean up the "/root/ISOs+luci-265.iso" type of stuff that appears in Rox persistently unless specifically deleted?
Found another bug. When I had first installed and started Seamonkey, it told me it needed flashplayer updated. I said go ahead and it apparently did it.
Then I went to youtube and tried to run this:
http://www.youtube.com/watch?v=21S_y0WH7x0
It said it couldn't run it because I needed to update flashplayer!
It offered some options but they are not good for installing in puppy. I then remembered to try PPM, and installed flashplayer-10.3.181.34-lucid
At the end it told me a lot of libraries were missing (e.g. libkdecore.so.5, libQtDbus.so.4, etc.). I couldn't find them in PPM so I gave up and tried running that youtube again, and it worked OK. So I don't know what the state of flashplayer is on my machine. Kinda worrysome...
Then I went to youtube and tried to run this:
http://www.youtube.com/watch?v=21S_y0WH7x0
It said it couldn't run it because I needed to update flashplayer!
It offered some options but they are not good for installing in puppy. I then remembered to try PPM, and installed flashplayer-10.3.181.34-lucid
At the end it told me a lot of libraries were missing (e.g. libkdecore.so.5, libQtDbus.so.4, etc.). I couldn't find them in PPM so I gave up and tried running that youtube again, and it worked OK. So I don't know what the state of flashplayer is on my machine. Kinda worrysome...
Luci265Béèm wrote:Installed the usual Lin'N'Win FRUGAL of 265
When clicking on the network icon in the tray, /var/cache/fontconfig it started to fill. I could stop it by restarting X otherwise this would have continued as in the 263.
manual frugal install + save file
This is not happening for me.
There are a few items in /var/cache/fontconfig
But nothing like you are seeing.
Last edited by bigpup on Sun 17 Jul 2011, 21:50, edited 1 time in total.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Luci265PaulBx1 wrote:Found another bug. When I had first installed and started Seamonkey, it told me it needed flashplayer updated. I said go ahead and it apparently did it.
Then I went to youtube and tried to run this:
http://www.youtube.com/watch?v=21S_y0WH7x0
It said it couldn't run it because I needed to update flashplayer!
Frugal install + save file
I just downloaded and installed Seamonkey.
At first run got message about Flashplayer download.
Downloaded and installed Flashplayer.
Shutdown and restarted Seamonkey as instructed by the Flashplayer install.
Tried your YouTube video.
Worked for me.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
I just recenly put this box together so I hadn't tried 5.2.5. Booted to a 800x600 desktop,used xorgwizard and was able to get either 1600x1200 or 1280x1024 with the vesa driver. Was making a post to that effect when everything froze up leading to a hard poweroff.playdayz wrote: James C, Did that nasty Nvidia 8400 work correctly with Lucid 5.2.5?
Posting this now from my Mageia install which has no problems on the exact same hardware.
Don't know if the problem is in the detection, the vesa driver itself or the lack of the dreaded nouveau driver.
The strange thing is, on another box( Windows 7,PCLOS and Lucid 5.2.5) with a Nvidia 8400GS card....regular PCI instead of PCI-X......no problems at all.
I love testing.......
I have to admit that I have got one total freezing also with luci 265
I even didnt do anything special. No installing of apps, well, maybe something small, useful from my own luci apps depot in hdd.
I have got similar freezening sometimes with my own puplets with experimental kernels but I dont recall that has happened with official versions before. Mostly they have happened ramdomly.
Maybe coincidence but it would be good if other people reports if it has happened to them.
I even didnt do anything special. No installing of apps, well, maybe something small, useful from my own luci apps depot in hdd.
I have got similar freezening sometimes with my own puplets with experimental kernels but I dont recall that has happened with official versions before. Mostly they have happened ramdomly.
Maybe coincidence but it would be good if other people reports if it has happened to them.
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
We must find some way of adding that to dog biscuits . . .I love testing.......
Perhaps press releases from Playdayz, 01Micko and Barry when
needing more testers could be distributed to Linux news outlets?
Most major distros include beta and rc releases . . .
m m m . . . rambling . . .
Puppy Linux
Tested on geeks
Re: Luci-265 - 5th development release for Lucid 5.2.6
The transition into the 64 bit world has been ongoing for quite some time. It was only a quetion of time before puppy's direction would have to take it into account, seriously. With the advent of Intel's N570 (the new low end type of processor) puppy will just have to bite the bullet, and go for it.playdayz wrote:Luci-265...
After Lucid 5.2.6 is done, we will have a good basis for a Community Edition. I envision this as a larger than usual Puppy, with additional programs suggested by forum members. Maybe 160-180MB. Oh yes, with a more advanced kernel! Pemasu's work is a model for what I have in mind. At the same time we release the Community Edition wouldn't it be amazing if we could release a twin 64-bit edition! Or at least a "hybrid" 32/64 bit edition. Iguleder seems to have something going on there. You never know
There has been a lot of exciting experiments going on and I hope we can incorporate some of them into these new Puppies.
Cheers.
[b]ir[/b]