Wary Puppy 5.1.4 - 29 August 2011
audio.png icon
A problem is the audio icon when there is grey
background. (See the screenshots ) There
is a noticeable fringing effect around the audio.png icon
when grey is the background.
Jemimah solved this problem with a different icon.
I suggest a replacement for
/usr/local/apps/ROX-Filer/ROX/MIME/audio.png
with Jemimah's
/usr/local/apps/ROX-Filer/ROX/MIME/audio.png
Here's the improved result when the icon is changed.
____________________
background. (See the screenshots ) There
is a noticeable fringing effect around the audio.png icon
when grey is the background.
Jemimah solved this problem with a different icon.
I suggest a replacement for
/usr/local/apps/ROX-Filer/ROX/MIME/audio.png
with Jemimah's
/usr/local/apps/ROX-Filer/ROX/MIME/audio.png
Here's the improved result when the icon is changed.
____________________
- Attachments
-
- audio.png
- Jemimah's improved icon
- (2.16 KiB) Downloaded 1034 times
Wary Puppy 5.1.2.7 (5.1.3 beta)
Manual frugal install to gateway desktop.
Installed devx + kernel source sfs + ati-driver-installer-11-7-x86.x86_64.run
Tue 9 Aug 2011 Operating System: Wary Puppy-5.1.2.7 Linux 2.6.32.43
0.0 VGA compatible controller: ATI Technologies Inc Redwood PRO [Radeon HD 5500 Series]
oem: ATI ATOMBIOS product: REDWOOD 01.00
X Server: Xorg Driver: #card0driver
X.Org version: 1.3.0
dimensions: 1920x1080 pixels (521x293 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 5570
OpenGL version string: 4.1.10907 Compatibility Profile Context
AMD Phenom(tm) II X4 810 Processor
Core 0: 2593 1: 2593 2: 2593 3: 2593 MHz
# glxgears
39603 frames in 5.0 seconds = 7920.435 FPS
39756 frames in 5.0 seconds = 7951.052 FPS
39753 frames in 5.0 seconds = 7950.454 FPS
I chose probe on first boot and it used vesa at a lower resolution but
after creating a save file etc, and installing the proprietary driver
it's good.
Sound and wired network were good at first boot.
Installed devx + kernel source sfs + ati-driver-installer-11-7-x86.x86_64.run
Tue 9 Aug 2011 Operating System: Wary Puppy-5.1.2.7 Linux 2.6.32.43
0.0 VGA compatible controller: ATI Technologies Inc Redwood PRO [Radeon HD 5500 Series]
oem: ATI ATOMBIOS product: REDWOOD 01.00
X Server: Xorg Driver: #card0driver
X.Org version: 1.3.0
dimensions: 1920x1080 pixels (521x293 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 5570
OpenGL version string: 4.1.10907 Compatibility Profile Context
AMD Phenom(tm) II X4 810 Processor
Core 0: 2593 1: 2593 2: 2593 3: 2593 MHz
# glxgears
39603 frames in 5.0 seconds = 7920.435 FPS
39756 frames in 5.0 seconds = 7951.052 FPS
39753 frames in 5.0 seconds = 7950.454 FPS
I chose probe on first boot and it used vesa at a lower resolution but
after creating a save file etc, and installing the proprietary driver
it's good.
Sound and wired network were good at first boot.
G'day,
Frugal install to a new but el-cheapo desktop computer with ATI Radeon HD5450 graphics and a 1600x900 monitor.
The xorg wizard in Wary did not use the radeon driver when selected by <Choose> so I had to accept vesa and 1280x1024 graphics. Distorted geometry but just about everything else worked, sometimes in a slightly quirky way (e,g, re-drawing some windows was 'different').
Having had success using the pets made from the ATI Catalyst proprietary driver to fix graphics problems with lucid and dpups (even in 4.2.1) on this computer, I installed the lucid ATI pet to the Wary frugal. Did a console>aticonfig --initial to create a new xorg.conf and then a restartX. Now I get 1600x900 graphics although the ATI Catalyst Control Centre doesn't run. This result was similar to the radeon problem fix in dpup where a libdrm_radeon-2.4.21 file was found by stu90 to be missing. I could fix my dpups by installing pemasu's pet of this instead of the larger ATI Catalyst pet. But this didn't seem to fix the Wary graphics on this desktop.
I hope this may be of some use. Of course, I may be the only one having radeon problems like this.
Thanks again for Puppy.
David S.
Frugal install to a new but el-cheapo desktop computer with ATI Radeon HD5450 graphics and a 1600x900 monitor.
The xorg wizard in Wary did not use the radeon driver when selected by <Choose> so I had to accept vesa and 1280x1024 graphics. Distorted geometry but just about everything else worked, sometimes in a slightly quirky way (e,g, re-drawing some windows was 'different').
Having had success using the pets made from the ATI Catalyst proprietary driver to fix graphics problems with lucid and dpups (even in 4.2.1) on this computer, I installed the lucid ATI pet to the Wary frugal. Did a console>aticonfig --initial to create a new xorg.conf and then a restartX. Now I get 1600x900 graphics although the ATI Catalyst Control Centre doesn't run. This result was similar to the radeon problem fix in dpup where a libdrm_radeon-2.4.21 file was found by stu90 to be missing. I could fix my dpups by installing pemasu's pet of this instead of the larger ATI Catalyst pet. But this didn't seem to fix the Wary graphics on this desktop.
I hope this may be of some use. Of course, I may be the only one having radeon problems like this.
Thanks again for Puppy.
David S.
Sage wrote:JC: Please can you report the NIC type printed on top of your chip rather than from HardInfo? Thank you.JC:
Quote:
Ethernet controller : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
Is this a type 'D' as printed on the actual chip? Did anyone sort out the 8139D driver paradox?
That old box has an onboard nic and the mobo manufacturer refers to it as a Realtek RTL8100L .
Yes it is.The chip reads "RTL8100BL". (According to the old flashlight/magnifying glass method).Sage wrote:Yes, but what does it actually read on top of the chip?! Clearly it isn't an 8100, maybe not even an 8139C??That old box has an onboard nic and the mobo manufacturer refers to it as a Realtek RTL8100L .
http://www.realtek.com/products/product ... &ProdID=13
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: audio.png icon
Thanks, I have put that into rootfs-complete/usr/local/apps/ROX-Filer/ROX/MIME in Woof. This will ensure the new image will be used regardless of what ROX-Filer PET is used in the build -- so I don't have to try and modify all the Rox PETs out there!don570 wrote:A problem is the audio icon when there is grey
background. (See the screenshots ) There
is a noticeable fringing effect around the audio.png icon
when grey is the background.
Jemimah solved this problem with a different icon.
I suggest a replacement for
/usr/local/apps/ROX-Filer/ROX/MIME/audio.png
with Jemimah's
/usr/local/apps/ROX-Filer/ROX/MIME/audio.png
[url]https://bkhome.org/news/[/url]
Thanks, JC, that is very helpful - in a strange sort of way. Either HardInfo isn't reporting correctly or Realtek and their licensees aren't installing the correct microcode. Take your pick!Yes it is.The chip reads "RTL8100BL".
This leaves the issue of no drivers for chips actually marked 8139D; clearly an item for attention of BK and derivative developers.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
The reason that the Realtek RTL8100 chip reports itself as "RTL-8139/8139C/8139C+" is because Realtek considers the more recent RTL810X devices to be part of the older RTL8139X family, and their own (vendor-provided) Linux driver covers the entire range.James C wrote:Ethernet controller : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
...
That old box has an onboard nic and the mobo manufacturer refers to it as a Realtek RTL8100L
But the kernel developers see things differently; they support the older range with the 8139cp/8139too drivers, and the newer range with the r8169 driver.
Well the problem of RTL8139X failure was discussed, and partly solved in this post last February -Sage wrote:Did anyone sort out the 8139D driver paradox?
http://www.murga-linux.com/puppy/viewto ... 477#498477
For anyone experiencing problems with the Realtek 8139 device, my suggestion remains now as I suggested then; go to
Menu > System > BootManager configure bootup > Give preference to one module over another:
and add this line -
Code: Select all
8139cp:8139too
If not, reverse the line -
Code: Select all
8139too:8139cp
Once we know which preference setting works, the Wary/Quirky/Lucid developers can put this permanently in place.
Wow! Thanks a A$bn, tp. Nice to know there's a guy around with all the answers. Seems I missed your blast last Feb. Wonder how many other folks are having this trouble? It was easy for me to fix with a drawer-full of alternative NICs, but there are quite a few guys who are less than keen to open their boxes, much less tackle surgery on their mainboard, being the only other option to a SW fix. Without your assistance, the latter would've been well outside my personal ambit.
Could be a show-stopper? What's BK think about it all?
Later: calling Houston.
Used Wary 5.1.2.7 on FULL installation.
Followed your recipe, tp. Initially, 8139cp was already listed as preferred over 8139too. Reversed/rebooted. Tried 'too' and 'cp' drivers - nogo
Reversed preferred order again. Tried both drivers, as well as ne2k-pci, tulip & e1000.
Nada.
Run out of ideas. This NIC works OK on other distros - I think/thought, but will check against boxloads of kit/liveCDs.
Ah! Guess tp may be abed at this hour?
Could be a show-stopper? What's BK think about it all?
Later: calling Houston.
Used Wary 5.1.2.7 on FULL installation.
Followed your recipe, tp. Initially, 8139cp was already listed as preferred over 8139too. Reversed/rebooted. Tried 'too' and 'cp' drivers - nogo
Reversed preferred order again. Tried both drivers, as well as ne2k-pci, tulip & e1000.
Nada.
Run out of ideas. This NIC works OK on other distros - I think/thought, but will check against boxloads of kit/liveCDs.
Ah! Guess tp may be abed at this hour?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
What I suspect is happening is that both drivers have loaded, and are competing for the device. The modules-preference is supposed to prevent this, but we now know that the modules-preference is broken in Lucid, and Barry has recently mentioned that it should be fixed for Wary and Drake ... but maybe it's not??Sage wrote:8139cp was already listed as preferred over 8139too. Reversed/rebooted. Tried 'too' and 'cp' drivers - nogo
Reversed preferred order again.
If you want to solve the problem, you will need to take some aggressive technical action -
first remove all modules-preference entries relating to the 8139cp/8139too modules.
Now let's disable the 8139too driver - use ROX to go to /lib/modules/2.6.32/kernel/drivers/net and you will see "8139too.ko". Open a second ROX window, which should default to /root (~) and drag 8139too.ko into /root
Now run this command, which will "register" the new state of drivers -
Code: Select all
depmod-FULL
If the Network Wizard still doesn't show an ethernet interface, or the interface fails to connect, it would be worth running this command -
Code: Select all
dmesg
Of course, you could also reverse this situation - shift 8139cp.ko into /root (effectively disabling it) and shift 8139too.ko back into its correct location, then run the "depmod-FULL" command, and reboot.
[SOLVED] pwallpaper - new backgrounds
SOLVED - it was a file naming problem - see later posts
Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.
Nathan's wallpaper setter as used in other puppies does not have his problem.
cheers
peebee
Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.
Nathan's wallpaper setter as used in other puppies does not have his problem.
cheers
peebee
Last edited by peebee on Tue 16 Aug 2011, 18:24, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
OK, tp - did all that, and some more.
Nothing good to report. At the end of dmesg one sees the cp driver (re)load but nothing useful about eth0. Manually loading drivers didn't work either.
In the meantime, I tried liveCD of Peppermint and PCL-LXDE. Neither could call up the 8139D.
Although I got the impression that the NIC was working previously, I am driven to the conclusion that either I was mistaken and/or it isn't any longer! I guess the fact that its little green led was alight also gave a false impression. Stuck in an 8139C - no problems.
Sorry to have exercised your talents to no effect, but I now have a crystal and relay in my spares box...
Ah, but wait a mo - vide infra.
Nothing good to report. At the end of dmesg one sees the cp driver (re)load but nothing useful about eth0. Manually loading drivers didn't work either.
In the meantime, I tried liveCD of Peppermint and PCL-LXDE. Neither could call up the 8139D.
Although I got the impression that the NIC was working previously, I am driven to the conclusion that either I was mistaken and/or it isn't any longer! I guess the fact that its little green led was alight also gave a false impression. Stuck in an 8139C - no problems.
Sorry to have exercised your talents to no effect, but I now have a crystal and relay in my spares box...
Ah, but wait a mo - vide infra.
Last edited by Sage on Fri 12 Aug 2011, 14:11, edited 1 time in total.
NIC grief continued:
Having replaced the 8139D with an 8139C, I now find that this blighter won't work with my FULL installation. Moreover, there's a boot error message about this cr*p old Gigabyte Intel board GA-6WMMC7 (833AMD with 398MbSDRAM) that flashes by, not in dmesg, during boot-up with the FULL but not the liveCD.
The C now works OK with the liveCD but not the FULL: the 8139D works with neither.
If you're confused? Can you imagine what it does to my mind! When it comes to code, the best I can do is follow instructions. When it comes to HW, that's different!
In the fullness of time, I might try the D NIC in another board - not Intel chipset!
Later:
Stuck in a Pulse H1138 NIC in the Gigabyte. Signs up in HardInfo as Intel 82557/8/9/0/1 Ethernet Pro 100 - flawless! The mystery deepens.
Having replaced the 8139D with an 8139C, I now find that this blighter won't work with my FULL installation. Moreover, there's a boot error message about this cr*p old Gigabyte Intel board GA-6WMMC7 (833AMD with 398MbSDRAM) that flashes by, not in dmesg, during boot-up with the FULL but not the liveCD.
The C now works OK with the liveCD but not the FULL: the 8139D works with neither.
If you're confused? Can you imagine what it does to my mind! When it comes to code, the best I can do is follow instructions. When it comes to HW, that's different!
In the fullness of time, I might try the D NIC in another board - not Intel chipset!
Later:
Stuck in a Pulse H1138 NIC in the Gigabyte. Signs up in HardInfo as Intel 82557/8/9/0/1 Ethernet Pro 100 - flawless! The mystery deepens.
Sage
Found this on the web...
http://murga-linux.com/puppy/viewtopic.php?t=34881
HTH
Aitch
Found this on the web...
also referenced here, including possible acpi intereference....I Have making Realtek 8139D work with Mandriva One 2008.0
Mandriva will detect it and uses sc92031 module driver as the driver.
put this line in /etc/modprobe.conf
Code: Select all
alias eth0 sc92031
http://murga-linux.com/puppy/viewtopic.php?t=34881
HTH
Aitch
Black Screen
I downloaded Wary 5.1.2 a couple days ago, burned it to a CD (my ancient lappy won't boot from USB), and ran it (as a Live CD). It looked pretty good. Did some setup and a couple reboots...
On about the third reboot, and from then on, it boots to a black screen with a mouse X. The mouse works, but there's nothing for it to work on. There is a small icon top left which says I'm connected to the Internet. That's it.
Any ideas what I'm doing wrong or how to fix it? I also run MacPup this way and it works great.
On about the third reboot, and from then on, it boots to a black screen with a mouse X. The mouse works, but there's nothing for it to work on. There is a small icon top left which says I'm connected to the Internet. That's it.
Any ideas what I'm doing wrong or how to fix it? I also run MacPup this way and it works great.