Quirky 1.3 feedback and bug reports
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Quirky 1.3 feedback and bug reports
Quirky 1.3-final is released. I built it with the 2.6.33.2 kernel, not the latest.
See the announcement and links on my blog:
http://bkhome.org/blog/?viewDetailed=01822
To follow progress on Quirky:
http://bkhome.org/blog/?viewCat=Quirky
There was a 1.3RC forum thread:
http://murga-linux.com/puppy/viewtopic.php?t=60096
Feedback welcome!
See the announcement and links on my blog:
http://bkhome.org/blog/?viewDetailed=01822
To follow progress on Quirky:
http://bkhome.org/blog/?viewCat=Quirky
There was a 1.3RC forum thread:
http://murga-linux.com/puppy/viewtopic.php?t=60096
Feedback welcome!
[url]https://bkhome.org/news/[/url]
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
This is feedback on the RC but I hope the combination of Flash and Seamonkey is the same in the Final
I can watch streaming multimedia (just watched a BBC documentrary about the BBC) Will now be rebooting into the Final version. For some reason (I believe 64bit 'updates' of Adobe Flash 10.1) were not working in Puppy Lucid 5.1.1, Ubuntu, Squeeze etc. They would cut out at between 6 and 20 minutes.
Quirky is allowing me to watch streaming vids.
Many thanks
I can watch streaming multimedia (just watched a BBC documentrary about the BBC) Will now be rebooting into the Final version. For some reason (I believe 64bit 'updates' of Adobe Flash 10.1) were not working in Puppy Lucid 5.1.1, Ubuntu, Squeeze etc. They would cut out at between 6 and 20 minutes.
Quirky is allowing me to watch streaming vids.
Many thanks
Further to my initial reports on 'Barry's Blog"...
I have found that ndiswrapper is far more stable with my wg311v2 (netgear pci wireless, TI chipset) than tempestuous' driver which was, I think, compiled in Lupu, (slightly different kernel compile... that may be the cause IMO, and also NOT included in this quirky, for those concerned)
Also, I have an old TNT nvidia video card which defaults to the vesa driver. While that works fine, I can only get 1024x768 resolution with my old P3 with an old CRT. If I "choose" the 'nv' driver I get 1280x1024.. and acceleration. Is it worth the extra 5 meg to include the proprietary driver? (considering probably well over half of users don't have an nvidia, and another half of those have a compatible nvidia card with the driver, [those numbers are pure speculation!]).
Cheers
I have found that ndiswrapper is far more stable with my wg311v2 (netgear pci wireless, TI chipset) than tempestuous' driver which was, I think, compiled in Lupu, (slightly different kernel compile... that may be the cause IMO, and also NOT included in this quirky, for those concerned)
Also, I have an old TNT nvidia video card which defaults to the vesa driver. While that works fine, I can only get 1024x768 resolution with my old P3 with an old CRT. If I "choose" the 'nv' driver I get 1280x1024.. and acceleration. Is it worth the extra 5 meg to include the proprietary driver? (considering probably well over half of users don't have an nvidia, and another half of those have a compatible nvidia card with the driver, [those numbers are pure speculation!]).
Cheers
Puppy Linux Blog - contact me for access
Solid as ever.
I notice a slower boot-up time where the script shows a "pausing" indication in red. This is the point where it is looking for Puppy files. Runs very fast when loaded. Nice and stable - ideal for recommending to friends/clients.
I remember reading something about changes to the way the system searches for Puppy files at boot, but can't remember the details.
There's a lot of new Puppy versions appearing now on an on-going basis, so it's becoming a task in itself trying to test them all. Look at it like this:
Group A is Barry's base versions
Group B is non-Barry official versions e.g. (Puppy 511)
Group C is the Wild West where anything goes (Geeks' Paradise) e.g. Puppy Squeeze.
Group B uses stuff from both Groups A and B
Each of these groups has got prodigious output at the moment. No wonder Joe Public has problems deciding on anything to do with Linux. Other distros are also appearing on the scene thick and fast. Puppy's total output of new stuff is simply ballooning compared to only a short time ago.
Just been trying real Debian Squeeze 64 bit. Nice distro, but not as fast as 32 bit Puppy Squeeze.
So Puppy is still the nippiest, but I wonder if a 64-bit version would make it go even faster.
Can Woof be hooked up to the Debian or Ubuntu 64-bit packages specifically? I doubt if it's that simple though.
I notice a slower boot-up time where the script shows a "pausing" indication in red. This is the point where it is looking for Puppy files. Runs very fast when loaded. Nice and stable - ideal for recommending to friends/clients.
I remember reading something about changes to the way the system searches for Puppy files at boot, but can't remember the details.
There's a lot of new Puppy versions appearing now on an on-going basis, so it's becoming a task in itself trying to test them all. Look at it like this:
Group A is Barry's base versions
Group B is non-Barry official versions e.g. (Puppy 511)
Group C is the Wild West where anything goes (Geeks' Paradise) e.g. Puppy Squeeze.
Group B uses stuff from both Groups A and B
Each of these groups has got prodigious output at the moment. No wonder Joe Public has problems deciding on anything to do with Linux. Other distros are also appearing on the scene thick and fast. Puppy's total output of new stuff is simply ballooning compared to only a short time ago.
Just been trying real Debian Squeeze 64 bit. Nice distro, but not as fast as 32 bit Puppy Squeeze.
So Puppy is still the nippiest, but I wonder if a 64-bit version would make it go even faster.
Can Woof be hooked up to the Debian or Ubuntu 64-bit packages specifically? I doubt if it's that simple though.
Life is too short to spend it in front of a computer
rcrsn51 wrote:
This no show-stopper, but would be interesting to know what has changed.
Nope. In the case of running any previous Puppy on my normal PC deskdop hardware, I've only seldom had to use boot cheat codes. I normally boot from live CD and then make a pup_save file.Are you using the pdev1 and psubdir boot arguments?
This no show-stopper, but would be interesting to know what has changed.
Life is too short to spend it in front of a computer
Interesting this? With all previous Puppies, using my Acer Extensa laptop, intel graphics, if I tried to reduce/increase the screen brightness using the Fn/arrow up.down keys, I had to re-start X to make the changes visible. In 1.3, the brightness just goes up or down in real time (as it should)... cool.
Spup Frugal HD and USB
Root forever!
Root forever!
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Booting from CD, the init script mounts each hd partition in turn, and looks 2-deep for Puppy files. If they aren't found, it goes through the exercise again, looking 3-deep.tronkel wrote:I notice a slower boot-up time where the script shows a "pausing" indication in red. This is the point where it is looking for Puppy files. Runs very fast when loaded. Nice and stable - ideal for recommending to friends/clients.
Anyway, the "pause" message that you are getting is interesting. I found when testing the Intel Classmate, booting from USB optical drive, that although /dev/sr0 existed, it failed to mount -- a "sleep 5" then retry fixed it. This code was in earlier Woofs, but this time I have added the "pause" message.
So, you would have got that 5 second pause before, but without the "pause" message.
If the init script did have to drop down to a 3-deep scan, another message in purple text would have appeared.
So, I don't know why the scanning would be any slower in your case. Maybe your assessment is subjective? -- the "watched pot" syndrome? If it really is slower, that is curious and I wonder why.
[url]https://bkhome.org/news/[/url]
Quirky 1.3 ungood ThinkPad R51 with intel 852/855 GM
Have the iso from day before yesterday at which point I think it was still an RC. Sad to discover that my laptop ThinKPad R51 seems to be out in the cold. With Quirky 1.2 I could choose intel i810 and get a display. All I can get from 1.3 is the cold black hell of KMS darkness. Ungood. That is to say opting for 'intel' is no good and trying vesa is also no good. Too bad, I kind of liked Quirky.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Ethernet auto connected on my first boot - so I was net enabled.
Today it was gone and I had to set it..
Seamonkey and Flash combi still working great.
The time (I think I choose the second option 'utc')
is working OK - many wooflets have problems with providing the right time and I have to check my watch.
Today it was gone and I had to set it..
Seamonkey and Flash combi still working great.
The time (I think I choose the second option 'utc')
is working OK - many wooflets have problems with providing the right time and I have to check my watch.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Quirky 1.3 ungood ThinkPad R51 with intel 852/855 GM
You mean Wary. Quirky 1.2 did not offer the i810 driver, as the latest Xorg that will support it is Xorg 7.3.gnomic wrote:Have the iso from day before yesterday at which point I think it was still an RC. Sad to discover that my laptop ThinKPad R51 seems to be out in the cold. With Quirky 1.2 I could choose intel i810 and get a display. All I can get from 1.3 is the cold black hell of KMS darkness. Ungood. That is to say opting for 'intel' is no good and trying vesa is also no good. Too bad, I kind of liked Quirky.
Wary 0.7 has the choice of 'intel' and 'i810' Xorg drivers. The upcoming Wary 0.8 will too.
[url]https://bkhome.org/news/[/url]
Hi Barry,
There's a little problem with the window placement in the first shutting down + saving procedure.
The window that asks if you want a "normal" or an encrypted save-file is not centered on screen, but somewhat lowered. This hides the choice buttons.
Likewise for the window that asks if you want the pup.sfs moved from cd to hd.
This happens say two times in three fresh installs, so not every time.
I report it here as I noticed it in Quirky, but other Puppy's have this as well.( I reported it recently in the Puppy Squeeze thread.)
There's a little problem with the window placement in the first shutting down + saving procedure.
The window that asks if you want a "normal" or an encrypted save-file is not centered on screen, but somewhat lowered. This hides the choice buttons.
Likewise for the window that asks if you want the pup.sfs moved from cd to hd.
This happens say two times in three fresh installs, so not every time.
I report it here as I noticed it in Quirky, but other Puppy's have this as well.( I reported it recently in the Puppy Squeeze thread.)
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
Audio was not auto-detected at first. ( It is in Puppy5.xx and Squeeze)
Computer: Asrock Atom Ion 330.
So I ran the Alsa wizard. It found and installed a Nvidia driver, but still no sound.
Ran it again and it proposed three Nvidia drivers to choose from: Analogue, Digital and High Definition. I guessed "Digital" and sound was working.
So not a bug really, just a bit of a struggle.. ( a spoiled end user I am )
Computer: Asrock Atom Ion 330.
So I ran the Alsa wizard. It found and installed a Nvidia driver, but still no sound.
Ran it again and it proposed three Nvidia drivers to choose from: Analogue, Digital and High Definition. I guessed "Digital" and sound was working.
So not a bug really, just a bit of a struggle.. ( a spoiled end user I am )
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
BarryK wrote:
I'll have to eliminate the possibility of a bad ISO burn to CD. A gut-feeling tells me that this is a boot problem as such and may not necessarily related to the new method that has been implemented in order to search for Puppy files within nested folders. The MD5SUM for the ISO was OK.
I'll re-burn the ISO to CD using Puppy instead of Debian Squeeze this time and report back what I find.
This "pausing" message is displayed in red as a single word on my system. I have no nested Puppy folders on this system. So this message may well have existed within the start-up script for ages, but has never before appeared - maybe because it was never needed.So, you would have got that 5 second pause before, but without the "pause" message.
I'll have to eliminate the possibility of a bad ISO burn to CD. A gut-feeling tells me that this is a boot problem as such and may not necessarily related to the new method that has been implemented in order to search for Puppy files within nested folders. The MD5SUM for the ISO was OK.
I'll re-burn the ISO to CD using Puppy instead of Debian Squeeze this time and report back what I find.
Life is too short to spend it in front of a computer
Nope, same problem appears with the re-burned ISO.
The burner, which is also used to boot the live CD is an external USB device connected to the main PC via a USB hub.
This has never shown any problems before.
To summarise the problem:
Boot process starts as normal. When console display reaches the point "Searching for Puppy file in disc drives" it seems normal first of all. The CD drive then stops spinning, goes silent, and after another few seconds a single word "pausing" message gets displayed in red.
After a few seconds of this, boot is back to normal and at normal speed.
Has anything do do with the USB sub-system been changed in this version perhaps?
The "watched-pot" syndrome may well be a factor as well. The delay is not really very serious. Maybe I'm being over-
aware regarding boot times. I do this all the time LOL.
Since this something completely new - never before observed with any Puppy on this hardware (I must have booted virtually every Puppy version hundreds of times on this system), it would be interesting to know what the reason actually is for the message appearing.
I've forgotten how to get a dump of the start-up console text in Puppy.
I'll post a copy once I find out how to do this.
The burner, which is also used to boot the live CD is an external USB device connected to the main PC via a USB hub.
This has never shown any problems before.
To summarise the problem:
Boot process starts as normal. When console display reaches the point "Searching for Puppy file in disc drives" it seems normal first of all. The CD drive then stops spinning, goes silent, and after another few seconds a single word "pausing" message gets displayed in red.
After a few seconds of this, boot is back to normal and at normal speed.
Has anything do do with the USB sub-system been changed in this version perhaps?
The "watched-pot" syndrome may well be a factor as well. The delay is not really very serious. Maybe I'm being over-
aware regarding boot times. I do this all the time LOL.
Since this something completely new - never before observed with any Puppy on this hardware (I must have booted virtually every Puppy version hundreds of times on this system), it would be interesting to know what the reason actually is for the message appearing.
I've forgotten how to get a dump of the start-up console text in Puppy.
I'll post a copy once I find out how to do this.
Life is too short to spend it in front of a computer
Quirky 1.3 feedback and bug reports
I did a full install of quirky 1.3 final and I installed the nvidia driver from the ppm but glxgears doesn't work.
I compiled qt4 version 4.70 and then vlc 1.0.6 (I couldn't get 1.1.4 to compile) and I had to enter "--disable-glx" on the ./configure command line for vlc 1.0.6.
Vlc 1.0.6 compiled and there is no segfault when I exit vlc!
edit: I found an nvidia pet in the forum by Gray and applied that and now I have accelerated graphics and can use 3D games.
OpenGL
Vendor NVIDIA Corporation
Renderer GeForce 8600 GT/PCI/SSE2
Version 3.3.0 NVIDIA 256.44
Direct Rendering Yes
edit: I compiled fluxbox 1.1.1 and use that on both my laptop and desktop installs of quirky 1.3. I couldn't get wbar to compile but this is okay.I'm using the fluxbox menu (slightly edited) from my full install of Pupflux 5.1.1
edit: I made 22 pets using the new2dir script and tested them on a new full install on another pc and they work.
I compiled qt4 version 4.70 and then vlc 1.0.6 (I couldn't get 1.1.4 to compile) and I had to enter "--disable-glx" on the ./configure command line for vlc 1.0.6.
Vlc 1.0.6 compiled and there is no segfault when I exit vlc!
edit: I found an nvidia pet in the forum by Gray and applied that and now I have accelerated graphics and can use 3D games.
OpenGL
Vendor NVIDIA Corporation
Renderer GeForce 8600 GT/PCI/SSE2
Version 3.3.0 NVIDIA 256.44
Direct Rendering Yes
edit: I compiled fluxbox 1.1.1 and use that on both my laptop and desktop installs of quirky 1.3. I couldn't get wbar to compile but this is okay.I'm using the fluxbox menu (slightly edited) from my full install of Pupflux 5.1.1
edit: I made 22 pets using the new2dir script and tested them on a new full install on another pc and they work.
Last edited by Billtoo on Mon 27 Sep 2010, 08:01, edited 5 times in total.