The time now is Thu 20 Jun 2013, 02:48
All times are UTC - 4 |
| Author |
Message |
shinobar

Joined: 28 May 2009 Posts: 2271 Location: Japan
|
Posted: Sat 16 Oct 2010, 19:09 Post subject:
xorgwizard |
|
Regarding touchpad and keyboard(Japanese and Brazilian) issue,
I posted at another topic:
http://www.murga-linux.com/puppy/viewtopic.php?p=458996#458996
_________________ Multilingual Wary-511
Lucid Puppy Quickset edition
Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
|
Back to top
|
|
 |
Billtoo
Joined: 07 Apr 2009 Posts: 1508 Location: Ontario Canada
|
Posted: Sat 16 Oct 2010, 22:16 Post subject:
Wary Puppy 0.9 (090) feedback Subject description: ati graphics |
|
I'm running wary 090 kernel 2.6.30.5 live with a save file.
I've installed the kernel source sfs and devx sfs files.
Wireless network set up fine with sns and is persistent each boot-up.
Sound is not configured right away but running alsa wizard sets up the
sound okay however it must be set up again each boot-up.
I renamed depmod and depmod-FULL and downloaded and ran the ati driver:
ati-driver-installer-10-9-x86.x86_64.run and hardware acceleration *IS*
working.Nexuiz runs great
# report-video
VIDEO REPORT: Wary Puppy, version 090
Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00
Driver used by Xorg:
#card0driver
Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"
...the above also recorded in /tmp/report-video
#
Computer
Processor 4x Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz
Memory 3103MB (225MB used)
Operating System Puppy Linux 0.09
User Name root (root)
Date/Time Sat 16 Oct 2010 09:58:32 PM EDT
Display
Resolution 1600x900 pixels
OpenGL Renderer Unknown
X11 Vendor The X.Org Foundation
Operating System
Version
Kernel Linux 2.6.30.5 (i686)
Compiled #2 SMP Sat Sep 4 11:55:07 GMT-8 2010
C Library GNU C Library version 2.10.1 (stable)
Default C Compiler GNU C Compiler version 4.3.4 (GCC)
Distribution Puppy Linux 0.09
Current Session
Computer Name puppypc
User Name root (root)
Home Directory /root
Desktop Environment Unknown (Window Manager: JWM)
This Acer Aspire 7740G-6969 laptop has ATI mobility radeon hd 5470
graphics.
Edit: I added the dbus pets from the wary repo in ppm and then added some pets that I made in quirky 1.3.
The speaker icon in the tray is x'ed out each bootup but sound is working.
I tried wary 090 with the 2.6.35.7 kernel and it didn't see my wireless, same problem with 2.6.35.7 kernel on this laptop that I had on a desktop pc that I have, it can't see or load any network modules.
The 2.6.30.5 kernel works great but the 2.6.35.7 kernel doesn't.
Edit: I re-downloaded the wary 090 2.6.35.7 iso and checked the md5 sum and then used bootflash to install it to a flash drive and it is working fine so my dvd with 090 2.6.35.7 must have been a bad burn.
Last edited by Billtoo on Mon 18 Oct 2010, 00:06; edited 2 times in total
|
|
Back to top
|
|
 |
Billtoo
Joined: 07 Apr 2009 Posts: 1508 Location: Ontario Canada
|
Posted: Sun 17 Oct 2010, 10:08 Post subject:
Wary Puppy 0.9 (090) feedback Subject description: kernel 2.6.35.7 |
|
I installed the wary090 kernel 2.6.35.7 iso to a 4gb flash drive using
bootflash, set up the wireless network, sound was working on first
boot, rebooted to create save file and load the devx and kernel source
sfs files.
I renamed depmod and depmod-Full and exited to the prompt and ran the
ati-driver-installer-10-9-x86.x86_64.run file which enabled hardware
acceleration.
# report-video
VIDEO REPORT: Wary Puppy, version 090
Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00
Driver used by Xorg:
#card0driver
Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"
...the above also recorded in /tmp/report-video
#
Computer
Processor 4x Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz
Memory 3103MB (341MB used)
Operating System Puppy Linux 0.09
User Name root (root)
Date/Time Sun 17 Oct 2010 09:39:56 AM EDT
Display
Resolution 1600x900 pixels
OpenGL Renderer Unknown
X11 Vendor The X.Org Foundation
I added the dbus pets from the wary repo in ppm and then added some
pets,vlc,seamonkey208,pidgin2.7.3 and others.
It's working great
|
|
Back to top
|
|
 |
DaveS

Joined: 09 Oct 2008 Posts: 3697 Location: UK
|
Posted: Sun 17 Oct 2010, 10:52 Post subject:
|
|
The Open Office problem with the '35 kernel is a bit of a show stopper really.
_________________ Spup Frugal HD and USB
Root forever!
|
|
Back to top
|
|
 |
DaveS

Joined: 09 Oct 2008 Posts: 3697 Location: UK
|
Posted: Mon 18 Oct 2010, 02:21 Post subject:
|
|
'30 Kernel
Mplayer has no video output at 32 bit. Files play and sound can be heard but screen is just uniform yellow (or black in browser plug-in)
But it is ok at 16 bit
-Computer-
Processor : 2x Intel(R) Pentium(R) Dual CPU T2330 @ 1.60GHz
Memory : 1024MB (201MB used)
Operating System : Puppy Linux 0.09
User Name : root (root)
Date/Time : Mon 18 Oct 2010 07:19:37 BST
-Display-
Resolution : 1280x800 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA Intel
-Input Devices-
AT Translated Set 2 keyboard
SynPS/2 Synaptics TouchPad
Power Button
Lid Switch
Sleep Button
PC Speaker
HDA Digital PCBeep
Video Bus
b43-phy0
-Printers (CUPS)-
CUPS-PDF
HP : <i>Default</i>
-SCSI Disks-
ATA WDC WD800BEVS-22
TSSTcorp CDDVDW TS-L632H
Intel video.
[/u]
_________________ Spup Frugal HD and USB
Root forever!
Last edited by DaveS on Mon 18 Oct 2010, 07:57; edited 1 time in total
|
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 1507 Location: Baltimore, Maryland USA
|
Posted: Mon 18 Oct 2010, 07:26 Post subject:
|
|
| DaveS wrote: | | The Open Office problem with the '35 kernel is a bit of a show stopper really. |
Total show stopper in terms of having a system that can be used in a business environment.
Noticed the same problem with a bootable USB setup if that's any help.
Thom
|
|
Back to top
|
|
 |
DaveS

Joined: 09 Oct 2008 Posts: 3697 Location: UK
|
Posted: Tue 19 Oct 2010, 07:18 Post subject:
|
|
Confirming OpenOffice problem with .sfs, '35 Kernel. I downloaded the latest OO with the evil Oracle branding, built a new .sfs and it still totally locks up the system requiring a hard re-start.
I did not try with a .pet install, cant see why it should be any different.
_________________ Spup Frugal HD and USB
Root forever!
|
|
Back to top
|
|
 |
ICPUG
Joined: 24 Jul 2005 Posts: 1278 Location: UK
|
Posted: Tue 19 Oct 2010, 08:13 Post subject:
|
|
Beem,
I have been looking at your latest posts (Friday - Saturday) regarding your save file problem. You ask a lot of questions and I think the answer to most of them is that the new init script coping with simple filenames is probably the cause of most of it.
I am not saying the new init script is better or worse - I haven't looked at it yet. I was quite intrigued when Barry first mentioned it on his blog as it might have brought back (in a different way) some of the changes we made in 4.2.1 to speed up booting when psubdir, etc is specified. It may be that the new init script is better and that we have to modify our behaviour a bit to get things working as we would like.
I am getting a little unclear as to where you put your files. In your early posts you state the puppy files are on sda1 with the save file on sda2. In your Friday post you say you copy the wary sfs to /mnt/home - which is on sda2. Do you do something on first run and then change the file position?
I would suggest removing the wary sfs file from sda1 once you have copied it to /mnt/home on sda2. Now it will be impossible to find it on sda1 and I wonder what happens now. I think wary in the new scheme of things will use the first it finds if there is more than 1 which may be why your pupstate does not reflect the movement. I am hoping my suggestion resolves this.
I am not sure why you don't keep your sfs files with the pupsave file anyway.
The way I operate is to keep my vmlinuz, initrd.gz, pupXXX.sfs and pupsaveXXX.2fs all in a subdirectory on a separate partition from my Windows partition (in my case sda5). The menu.lst is altered accordingly to point to vmlinuz and initrd.gz. I personally use PMEDIA, PDEV1 and PSUBDIR as well so that I don't get a choice of save files - just the right one to go with my selected puppy.
This isolates my puppies from each other as well as from Windows. The only problem I have run into is when I recently ran a Puppy Live CD for testing purposes forgetting that it searches everywhere and it tried to update one of the pupsave files it found! It had been so long since I ran a Live CD I forgot about the necessity for pfix=ram!
One of your queries in this thread and elsewhere is why the change in filename from wary-xxx.sfs to wary_xxx.sfs.
Barry did mention this in his blog somewhere.
If you remember filenames always used to be underscore and not hyphen. When it changed a lot of people found they were getting file not found errors because if they used Windows tools they found the hyphen got changed to an underscore. (This was all to do with CD file formats).
|
|
Back to top
|
|
 |
DaveS

Joined: 09 Oct 2008 Posts: 3697 Location: UK
|
Posted: Tue 19 Oct 2010, 09:25 Post subject:
|
|
For the sake of completeness, tried Open Office as a .pet install. Same problem, so it is nothing to do with .sfs handling I guess.
_________________ Spup Frugal HD and USB
Root forever!
|
|
Back to top
|
|
 |
Béèm

Joined: 21 Nov 2006 Posts: 11782 Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
|
Posted: Tue 19 Oct 2010, 15:30 Post subject:
|
|
| ICPUG wrote: | Beem,
I have been looking at your latest posts (Friday - Saturday) regarding your save file problem. You ask a lot of questions and I think the answer to most of them is that the new init script coping with simple filenames is probably the cause of most of it.
I am not saying the new init script is better or worse - I haven't looked at it yet. I was quite intrigued when Barry first mentioned it on his blog as it might have brought back (in a different way) some of the changes we made in 4.2.1 to speed up booting when psubdir, etc is specified. It may be that the new init script is better and that we have to modify our behaviour a bit to get things working as we would like.
I am getting a little unclear as to where you put your files. In your early posts you state the puppy files are on sda1 with the save file on sda2. In your Friday post you say you copy the wary sfs to /mnt/home - which is on sda2. Do you do something on first run and then change the file position?
I would suggest removing the wary sfs file from sda1 once you have copied it to /mnt/home on sda2. Now it will be impossible to find it on sda1 and I wonder what happens now. I think wary in the new scheme of things will use the first it finds if there is more than 1 which may be why your pupstate does not reflect the movement. I am hoping my suggestion resolves this.
I am not sure why you don't keep your sfs files with the pupsave file anyway.
The way I operate is to keep my vmlinuz, initrd.gz, pupXXX.sfs and pupsaveXXX.2fs all in a subdirectory on a separate partition from my Windows partition (in my case sda5). The menu.lst is altered accordingly to point to vmlinuz and initrd.gz. I personally use PMEDIA, PDEV1 and PSUBDIR as well so that I don't get a choice of save files - just the right one to go with my selected puppy.
This isolates my puppies from each other as well as from Windows. The only problem I have run into is when I recently ran a Puppy Live CD for testing purposes forgetting that it searches everywhere and it tried to update one of the pupsave files it found! It had been so long since I ran a Live CD I forgot about the necessity for pfix=ram!
One of your queries in this thread and elsewhere is why the change in filename from wary-xxx.sfs to wary_xxx.sfs.
Barry did mention this in his blog somewhere.
If you remember filenames always used to be underscore and not hyphen. When it changed a lot of people found they were getting file not found errors because if they used Windows tools they found the hyphen got changed to an underscore. (This was all to do with CD file formats). | I consider the puppy files in their respective directories on sda1 only a way to boot, like from a CD.
Once on the desktop I don't need sda1 and it isn't mounted anymore which suits me very well, as it is the Windows partition and I don't like it to be mounted and open for anything coming in through wine.
I operated this way from certainly 3.xx on. For 2.xx I am not sure.
In the puppy boot process when booting with pfix=ram I always see that the puppy sfs is copied to /mnt/home. Therefor I make sure it is done. If it isn't done correctly, I have a kernel panic.
In puppy 3.xx this cause me problems as the puppy sfs file all had the same name, but a different contents for different releases.
Happily this changed somewhere in 4.xx.
Therefor as soon as I saw Barry's idea to use simplified names, I knew I would run into problems.
So yes indeed I think also that the new approach of the initrd causes what I experience now.
I'll do a test to see if the sda1 is still mounted also when the wary_090 is made inoperable in sda1. I'll let know.
I must have missed the information in the blog for the change to use the underscore.
_________________ Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
|
|
Back to top
|
|
 |
Béèm

Joined: 21 Nov 2006 Posts: 11782 Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
|
Posted: Tue 19 Oct 2010, 15:56 Post subject:
|
|
| Béèm wrote: | | ICPUG wrote: | Beem,
I have been looking at your latest posts (Friday - Saturday) regarding your save file problem. You ask a lot of questions and I think the answer to most of them is that the new init script coping with simple filenames is probably the cause of most of it.
I am not saying the new init script is better or worse - I haven't looked at it yet. I was quite intrigued when Barry first mentioned it on his blog as it might have brought back (in a different way) some of the changes we made in 4.2.1 to speed up booting when psubdir, etc is specified. It may be that the new init script is better and that we have to modify our behaviour a bit to get things working as we would like.
I am getting a little unclear as to where you put your files. In your early posts you state the puppy files are on sda1 with the save file on sda2. In your Friday post you say you copy the wary sfs to /mnt/home - which is on sda2. Do you do something on first run and then change the file position?
I would suggest removing the wary sfs file from sda1 once you have copied it to /mnt/home on sda2. Now it will be impossible to find it on sda1 and I wonder what happens now. I think wary in the new scheme of things will use the first it finds if there is more than 1 which may be why your pupstate does not reflect the movement. I am hoping my suggestion resolves this.
I am not sure why you don't keep your sfs files with the pupsave file anyway.
The way I operate is to keep my vmlinuz, initrd.gz, pupXXX.sfs and pupsaveXXX.2fs all in a subdirectory on a separate partition from my Windows partition (in my case sda5). The menu.lst is altered accordingly to point to vmlinuz and initrd.gz. I personally use PMEDIA, PDEV1 and PSUBDIR as well so that I don't get a choice of save files - just the right one to go with my selected puppy.
This isolates my puppies from each other as well as from Windows. The only problem I have run into is when I recently ran a Puppy Live CD for testing purposes forgetting that it searches everywhere and it tried to update one of the pupsave files it found! It had been so long since I ran a Live CD I forgot about the necessity for pfix=ram!
One of your queries in this thread and elsewhere is why the change in filename from wary-xxx.sfs to wary_xxx.sfs.
Barry did mention this in his blog somewhere.
If you remember filenames always used to be underscore and not hyphen. When it changed a lot of people found they were getting file not found errors because if they used Windows tools they found the hyphen got changed to an underscore. (This was all to do with CD file formats). | I consider the puppy files in their respective directories on sda1 only a way to boot, like from a CD.
Once on the desktop I don't need sda1 and it isn't mounted anymore which suits me very well, as it is the Windows partition and I don't like it to be mounted and open for anything coming in through wine.
I operated this way from certainly 3.xx on. For 2.xx I am not sure.
In the puppy boot process when booting with pfix=ram I always see that the puppy sfs is copied to /mnt/home. Therefor I make sure it is done. If it isn't done correctly, I have a kernel panic.
In puppy 3.xx this cause me problems as the puppy sfs file all had the same name, but a different contents for different releases.
Happily this changed somewhere in 4.xx.
Therefor as soon as I saw Barry's idea to use simplified names, I knew I would run into problems.
So yes indeed I think also that the new approach of the initrd causes what I experience now.
I'll do a test to see if the sda1 is still mounted also when the wary_090 is made inoperable in sda1. I'll let know.
I must have missed the information in the blog for the change to use the underscore. | Wary 090 wants the wary_090.sfs on sda1.
At the point of switch root I got a kernel panic. So the init script doesn't look on sda2. Altho the message before the switch was that wary_090.sfs was loaded.
Also I come to a certain conclusion that the new init script fills in parameters if not given in the kernel line. Example in my case PDEV1='sda1' which I didn't supply anywhere.
I think the same is true for PSUBDIR=
Another reason for having my save files on another partition is, that sda1 was rapidly out of space. A certain moment I had save files of 512MB.
_________________ Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
|
|
Back to top
|
|
 |
ICPUG
Joined: 24 Jul 2005 Posts: 1278 Location: UK
|
Posted: Wed 20 Oct 2010, 07:42 Post subject:
|
|
I think what you are telling me Beem is that Wary wants puppy sfs on sda1 if you do not specify pdev1 (which you don't). I really must install Quirky 1.3 or Wary 0.9 to see what happens when you specify pdev1 as I do. It would be a fail in my eyes if it did not respect pdev1.
It seems what may have changed is the default behaviour. Previously puppy searched everywhere - now it only searches sda1 by default.
This copying of the sfs to /mnt/home by puppy is something Barry introduced in series 4 (I think). If you keep the save file and the sfs file in the same folder it does not happen.
You say the sfs is on sda1 purely for boot up but you have still not answered why you cannot put it with the save file on sda2 right from the get go. Even more reason if sda1 was getting short of space. OK the default option of Wary90 seems to fail with this configuration but we don't know what happens when pdev1 is specified.
This post in the comments to 'Welcome 1st Boot' entry on Barry's blog seems to show he is doing some work on the init script.
Quote
Posted on 20 Oct 2010, 8:57 by BarryK
Re welcome
It is in Woof, so applies to all builds.
Um, I really should upload the latest Woof. I was holding off until I had fully debugged the file-finding in the init script, which currently has a few issues. Well, I will see if I can get that sorted out pronto.
Unquote
|
|
Back to top
|
|
 |
maddox
Joined: 28 Sep 2007 Posts: 453 Location: sometimes in France
|
Posted: Wed 20 Oct 2010, 19:05 Post subject:
|
|
battery tray icon:
doesn't display charge rate or color. Clicking on batt tray icon displays a pop-up box with contents from /proc/acpi/battery/BAT1 and BAT2 slots
.. seems that maybe the slot/file info is mixed up in this powerapplet_tray.
Tried replacing the file from quirky-13/wary-06, charge rate & color is restored but update time is variable (worst case 2~3min).
rebooted live-cd, then waited 1 min for welcome msg to disappear (/var/log/messages tz time/date skew, another post)
unplugged AC : screen goes to lowest brightness level and laptop charge led switches off after 1~2 sec
plugged in AC : backplane brightnes is directly restored, but there is a 16~18 sec delay before laptop battery charge led switches on (this was rather fast in other versions, 1~2 sec delay)
if I unplug AC, then wait 3~12 sec & replugin AC and click on batt icon in tray before the imparted delay, I get a 'charging state: charged'
after the delay it indicates 'charging state: charging'
from a translators point of view : the battery pop-up box reveals a lot of usefull info for those who speak the lingo,
a colored icon is nearly universal & does show me when it's nearly out of juice, albeit the hover tooltip.
My laptop battery is rather tired : 'design capacity: 4400 mAh' 'last full capacity: 2554 mAh' ~53% usefull capacity left
nice to see the atiX600 16 bit color depth work.
|
|
Back to top
|
|
 |
ICPUG
Joined: 24 Jul 2005 Posts: 1278 Location: UK
|
Posted: Thu 21 Oct 2010, 07:23 Post subject:
|
|
Following up my last post.
I have now installed Quirky 1.3. You are right Beem. If the sfs is not on sda1 and you do not specify PDEV1 etc it does not get found.
However, my approach of storing everything on a non-windows partition (sda5) AND SPECIFYING PMEDIA, PDEV1, PSUBDIR still works.
Barry's blog says he is now testing a fix to solve your problem so it looks as if you may have two solutions!
|
|
Back to top
|
|
 |
peebee

Joined: 21 Sep 2008 Posts: 932 Location: Malvern, Worcs, UK
|
Posted: Thu 21 Oct 2010, 08:44 Post subject:
No DVB-T support |
|
One of my "New Puppy" tests is to see if digital TV DVB-T works:
wary090 - mplayer does not seem to support DVB-T which is a shame? unless I've missed something
luci232 - DVB-T works just great
dpup010 - same mplayer as luci232 but it just flashes the window a lot and then dies.
Cheers
Peter
|
|
Back to top
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|