Hello,
Would it be possible to replace fbpanel by lxpanel?
Lucid Puppy 5.2.7 RC2
-
ASRI éducation
- Posts: 3197
- Joined: Sat 09 May 2009, 12:10
- Location: France
- Contact:
[quotejim3560, That's good news. It didn't connect with luci-264 but it did with luci 265, am I right?[/quote]
playdayz, correct it did not connect with 264, did with 265 after first reboot. Now on 2nd reboot it failed. same old same old. sns acquired connection but the script timed out. see below. after installing your Frisbee pet worked as expected.
Information about this interface:
Interface: eth1 Driver: wl Bus: x MacAddress: AC:81:12:1D:A9:5E
Description: x
STEP1a: ifconfig eth1 up
STEP1b: iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:22:2D:E2:D5:31
ESSID:"E2D52D"
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:1/5 Signal level:-84 dBm Noise level:-90 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Cell 02 - Address: 3C:EA:4F:C3:6F:09
ESSID:"2WIRE124"
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:1/5 Signal level:-86 dBm Noise level:-90 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 03 - Address: 00:19:E4:4B:D3:19
ESSID:"2WIRE789"
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:5/5 Signal level:-52 dBm Noise level:-93 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
STEP1c: ifconfig eth1 down
STEP2: iwconfig eth1 mode managed
STEP3: iwconfig eth1 channel 10
STEP4: iwconfig eth1 essid "2WIRE789"
STEP5: iwconfig eth1 key restricted 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
STEP5: iwconfig eth1 key open 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
*********************************************************
LAST 10 LINES of /var/log/messages:
Jul 19 00:09:42 puppypc user.info kernel: registered panic notifier
Jul 19 00:09:42 puppypc user.info kernel: acpi device:01: registered as cooling_device2
Jul 19 00:09:42 puppypc user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
Jul 19 00:09:42 puppypc user.info kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 19 00:09:42 puppypc user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Jul 19 00:09:42 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A disabled
Jul 19 00:09:42 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jul 19 00:09:42 puppypc user.debug kernel: wl 0000:03:00.0: setting latency timer to 64
Jul 19 00:09:42 puppypc user.warn kernel: eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.60.48.36
Jul 19 00:09:42 puppypc user.info kernel: HDMI hot plug event: Pin=6 Presence_Detect=1 ELD_Valid=0
playdayz, correct it did not connect with 264, did with 265 after first reboot. Now on 2nd reboot it failed. same old same old. sns acquired connection but the script timed out. see below. after installing your Frisbee pet worked as expected.
Information about this interface:
Interface: eth1 Driver: wl Bus: x MacAddress: AC:81:12:1D:A9:5E
Description: x
STEP1a: ifconfig eth1 up
STEP1b: iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:22:2D:E2:D5:31
ESSID:"E2D52D"
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:1/5 Signal level:-84 dBm Noise level:-90 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Cell 02 - Address: 3C:EA:4F:C3:6F:09
ESSID:"2WIRE124"
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:1/5 Signal level:-86 dBm Noise level:-90 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 03 - Address: 00:19:E4:4B:D3:19
ESSID:"2WIRE789"
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:5/5 Signal level:-52 dBm Noise level:-93 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
STEP1c: ifconfig eth1 down
STEP2: iwconfig eth1 mode managed
STEP3: iwconfig eth1 channel 10
STEP4: iwconfig eth1 essid "2WIRE789"
STEP5: iwconfig eth1 key restricted 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
STEP5: iwconfig eth1 key open 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
*********************************************************
LAST 10 LINES of /var/log/messages:
Jul 19 00:09:42 puppypc user.info kernel: registered panic notifier
Jul 19 00:09:42 puppypc user.info kernel: acpi device:01: registered as cooling_device2
Jul 19 00:09:42 puppypc user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
Jul 19 00:09:42 puppypc user.info kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 19 00:09:42 puppypc user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Jul 19 00:09:42 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A disabled
Jul 19 00:09:42 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jul 19 00:09:42 puppypc user.debug kernel: wl 0000:03:00.0: setting latency timer to 64
Jul 19 00:09:42 puppypc user.warn kernel: eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.60.48.36
Jul 19 00:09:42 puppypc user.info kernel: HDMI hot plug event: Pin=6 Presence_Detect=1 ELD_Valid=0
Most of this can be ignored; see my next comment below.
I posted the following at the end of the bug thread dealing with pfix=fsck for encrypted pupsaves:
I posted the following at the end of the bug thread dealing with pfix=fsck for encrypted pupsaves:
It looks like he started putting it together and was getting nowhere, so lost interest. Kinda half-baked code...OK I was looking at the code in the init script to fsck encrypted pupsaves (starts at line 900 in the luci version). Found a couple of questionable things.
1) Part of it deals with enlarging the pupsave, if that is called for; and Barry increased it using "dd if=/dev/zero". This is poor practice cryptographically; he should be using /dev/urandom. No doubt, in the original creation of the pupsave in rc.shutdown, /dev/zero is also incorrectly being used for encrypted pupsaves.
2) He is using losetup in places rather than losetup-FULL. How can that work at all? You need losetup-FULL for encryption, because the busybox version does not have the -e parameter. It makes me wonder why we carry around these busybox versions of -FULL commands at all; we could get rid of them by using a modified PATH, so only -FULL versions are used.
3) I notice he is using extra modprobes, such as "modprobe aes_generic". I haven't been using aes_generic, but only aes, when I manually fsck the pupsave. I wonder what is going on here...
4) He tries to use the -p parameter in losetup, but neither the full nor busybox version has that parameter. To get xor encryption it should be the "-E 1" parameter, apparently (I'm not very familiar with the xor encryption).
Last edited by PaulBx1 on Mon 18 Jul 2011, 17:02, edited 1 time in total.
final rework of the i915 modeset business
Playdayz,
After posting my i915_update-1 a page back, I spent the day researching further on the ideas for coping with the black screen issue. The outcome is discouraging. A few ideas, but they never really solved the problem. And even if a PC boots up with one of the solutions, I may suddenly go black later on. Although improvements may have been made in later kernels, the i845 chipsets -- which simply cannot handle the modeset 1 (running Kernel Mode Setting) -- appear doomed. Most advice is to set the mode at 0 (User Mode Setting), which is good for kernel 2.6.33, but is no longer supported in later kernels. No mention is made of just not setting anything, but it seems to work for me.
After all that, I conclude that I should not change the method (modeset=0) already in use in luci, since it makes the most sense. But I want to provide options for those caught up in the i845 blackscreen saga. Therefore, the attached package makes it simple for a user to try omitting the modeset by a simple edit of the i915 rules file. The config file checks for either of two flags (for 0 or nothing); if neither is set, mode 1 is used. Keep in mind that this applies only to the rules for the troublesome cards; all other cards/chipsets use mode 1.
One thing I added as a precaution, is to ensure that the fbcon module gets loaded before i915. That is from advice that if i915 loaded first, it would not have the resources provided by fbcon. That might be important for multiple processors/cores.
So, the function is unchanged, but supports more possibilities. I have now exhausted my effort to fix all the blackscreens -- it is just not possible. But I have learned a lot, and am still ready to add cards to the rules file for other i915-problem graphics cards, as I am notified of them.
Richard
After posting my i915_update-1 a page back, I spent the day researching further on the ideas for coping with the black screen issue. The outcome is discouraging. A few ideas, but they never really solved the problem. And even if a PC boots up with one of the solutions, I may suddenly go black later on. Although improvements may have been made in later kernels, the i845 chipsets -- which simply cannot handle the modeset 1 (running Kernel Mode Setting) -- appear doomed. Most advice is to set the mode at 0 (User Mode Setting), which is good for kernel 2.6.33, but is no longer supported in later kernels. No mention is made of just not setting anything, but it seems to work for me.
After all that, I conclude that I should not change the method (modeset=0) already in use in luci, since it makes the most sense. But I want to provide options for those caught up in the i845 blackscreen saga. Therefore, the attached package makes it simple for a user to try omitting the modeset by a simple edit of the i915 rules file. The config file checks for either of two flags (for 0 or nothing); if neither is set, mode 1 is used. Keep in mind that this applies only to the rules for the troublesome cards; all other cards/chipsets use mode 1.
One thing I added as a precaution, is to ensure that the fbcon module gets loaded before i915. That is from advice that if i915 loaded first, it would not have the resources provided by fbcon. That might be important for multiple processors/cores.
So, the function is unchanged, but supports more possibilities. I have now exhausted my effort to fix all the blackscreens -- it is just not possible. But I have learned a lot, and am still ready to add cards to the rules file for other i915-problem graphics cards, as I am notified of them.
Richard
- Attachments
-
- i915_update-2.pet
- flexible i915 modeset package
- (3.34 KiB) Downloaded 220 times
Testing this release I decided to try Dillo, something I haven't used before.
What a delight, light, simple and fast.
What should be compulsory reading to any Puppyite is the
story in the sidebar. "The Right to Read" stick with it to the end,
it's fascinating.
(If you read it, then yes, I'm aware of the irony in the use of "compulsory")
What a delight, light, simple and fast.
What should be compulsory reading to any Puppyite is the
story in the sidebar. "The Right to Read" stick with it to the end,
it's fascinating.
(If you read it, then yes, I'm aware of the irony in the use of "compulsory")
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
ASRI éducation
- Posts: 3197
- Joined: Sat 09 May 2009, 12:10
- Location: France
- Contact:
In RMLL2011 (Strasbourg France), I had the opportunity to meet one of the developers of Gnumeric and Abiword.
He said:
- Abiword 2.9 is not a good idea, because it is a development version (cf. discussion about package Abiword 2.9 by ttuuxxx).
- Gnumeric v1.10.16 provides a set of interesting patches.
He said:
- Abiword 2.9 is not a good idea, because it is a development version (cf. discussion about package Abiword 2.9 by ttuuxxx).
- Gnumeric v1.10.16 provides a set of interesting patches.
Luci-265 - 5th development release for Lucid 5.2.6
I did a manual frugal install of 265 and installed xorg-high and then
the ati pet in quickpet.
Mon 18 Jul 2011 Operating System: Lucid Puppy-265 Linux 2.6.33.2
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: (II) glx: vendor=FireGL - ATI Technologies Inc. (II) Module fglrx: vendor=FireGL - ATI Technologies Inc. (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc.
X.Org version: 1.7.6
dimensions: 1920x1080 pixels (507x285 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 5500 Series
OpenGL version string: 4.0.10243 Compatibility Profile Context
AMD Phenom(tm) II X4 810 Processor
Core 0: 2592 1: 2592 2: 2592 3: 2592 MHz
sh-4.1# glxgears
38850 frames in 5.0 seconds
38917 frames in 5.0 seconds
38948 frames in 5.0 seconds
No problems so far.
the ati pet in quickpet.
Mon 18 Jul 2011 Operating System: Lucid Puppy-265 Linux 2.6.33.2
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: (II) glx: vendor=FireGL - ATI Technologies Inc. (II) Module fglrx: vendor=FireGL - ATI Technologies Inc. (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc.
X.Org version: 1.7.6
dimensions: 1920x1080 pixels (507x285 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 5500 Series
OpenGL version string: 4.0.10243 Compatibility Profile Context
AMD Phenom(tm) II X4 810 Processor
Core 0: 2592 1: 2592 2: 2592 3: 2592 MHz
sh-4.1# glxgears
38850 frames in 5.0 seconds
38917 frames in 5.0 seconds
38948 frames in 5.0 seconds
No problems so far.
- Attachments
-
- 265scrn.jpg
- (112.45 KiB) Downloaded 712 times
-
ASRI éducation
- Posts: 3197
- Joined: Sat 09 May 2009, 12:10
- Location: France
- Contact:
How about that! I got a version of Google-Chrome running... latest version 12.0.742.124. First load from fresh boot it fails to load homepage, but closing and re-loading fixes it for that session. Otherwise it has been stable. No stupid 'root' issues either. Will run it against Peacemaker in a mo. If anyone wants I will create a .pet.
Spup Frugal HD and USB
Root forever!
Root forever!
Manual frugal install.
So far everything looks good and seems faster than lupu 525.
-Computer-
Processor : Intel(R) Pentium(R) 4 CPU 1.70GHz
Memory : 515MB (157MB used)
Operating System : Puppy Linux 0.26
User Name : root (root)
Date/Time : Mon 18 Jul 2011 12:35:38 PM EDT
-Display-
Resolution : 1280x1024 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE2
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH4 - Intel 82801DB-ICH4
-Input Devices-
AT Translated Set 2 keyboard
MosArt Optical Mouse
Power Button
Power Button
PC Speaker
-Printers (CUPS)-
CUPS-PDF
pdf_writer : <i>Default</i>
-SCSI Disks-
ATA MAXTOR 4K020H1
ATA ST320014A
ATAPI DVD A DH20A4P
So far everything looks good and seems faster than lupu 525.
-Computer-
Processor : Intel(R) Pentium(R) 4 CPU 1.70GHz
Memory : 515MB (157MB used)
Operating System : Puppy Linux 0.26
User Name : root (root)
Date/Time : Mon 18 Jul 2011 12:35:38 PM EDT
-Display-
Resolution : 1280x1024 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE2
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH4 - Intel 82801DB-ICH4
-Input Devices-
AT Translated Set 2 keyboard
MosArt Optical Mouse
Power Button
Power Button
PC Speaker
-Printers (CUPS)-
CUPS-PDF
pdf_writer : <i>Default</i>
-SCSI Disks-
ATA MAXTOR 4K020H1
ATA ST320014A
ATAPI DVD A DH20A4P
I added the following to the 525 bug thread:
Oh, and I noticed my keyboard is always in numlock whenever I press F2 at boot. No big deal, but could be annoying or confounding to some.As to this complaint about nonfunctionality of "puppy=fsck" for encrypted pupsaves:
http://www.murga-linux.com/puppy/viewto ... 176#545176
The solution is to uncomment the call to fsck the pupsave! Line 967 in luci 265, not sure where in 525.
Another bug: Barry, in rc.shutdown (where pupsaves are created) and in the init script (where pupsaves are enlarged), uses "dd if=/dev/zero". This is poor cryptographic practice for encrypted pupsaves. Should use /dev/urandom. I have tried it and it works, however it extends the time to create a pupsave (about 5 minutes for a 512MB one). In the init script it is no big deal because the extension of encrypted pupsaves is separate from that of non-encrypted ones; but in rc.shutdown it's all done in one place. So there, it should be conditional, depending on whether or not they want an encrypted pupsave, so most folks won't have to wait so long.
Last edited by PaulBx1 on Mon 18 Jul 2011, 17:15, edited 1 time in total.
Yes snail. Please accept my apologies. On the first message of this thread I indicated the the fix was present in 264--I meant it to be but I goofed. In 5.2.5 the syslinux 4 was fixed in the Instant Update. I am sorry for the inconvenience. And thanks for your testing.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.
Last edited by playdayz on Mon 18 Jul 2011, 17:13, edited 1 time in total.
Not in this upcoming release. However, when EZ-Woof 5.2.6 is posted, it would be possible for someone to do it themselves.Would it be possible to replace fbpanel by lxpanel?
Or, wait a minute, if we have a good pet of lxpanel that can be placed in the Puppy Package Manager and someone could install it before remastering.
Is there a good pet of lxpanel?
Here's one for testing ->
http://www.murga-linux.com/puppy/viewto ... 48&t=62757
Thanks for the good information. I was unable to compile Gnumeric 1.10.16 because it needed several updated versions of dependencies. Dave S says 1.10.13 is a good one, so unless someone comes through we will probably stay with it.- Gnumeric v1.10.16 provides a set of interesting patches.
Network interfaces not recognized/loaded on my new laptop
I'm testing this luci-265 release on my new laptop, a Packard Bell TM85, I3 370M processor, Nvida GT320M graphics.
No network interface is recognized.
The interfaces on it are:
Wired: Broadcom Netlink BCM57780 Gigabit
Wireless: Realtek RTL8192SE
The former should be loaded by the tg3 module, but it does not seem to work at all. For the latter I could not find a suitable module.
FatDog64 (latest) loads the tg3 driver correctly for my ethernet card, but no luck for the wireless part.
No network interface is recognized.
The interfaces on it are:
Wired: Broadcom Netlink BCM57780 Gigabit
Wireless: Realtek RTL8192SE
The former should be loaded by the tg3 module, but it does not seem to work at all. For the latter I could not find a suitable module.
FatDog64 (latest) loads the tg3 driver correctly for my ethernet card, but no luck for the wireless part.
Wyk72. Right thread for you.
http://www.murga-linux.com/puppy/viewto ... 469#462469
http://www.murga-linux.com/puppy/viewto ... 938#447938
http://www.murga-linux.com/puppy/viewto ... 469#462469
http://www.murga-linux.com/puppy/viewto ... 938#447938
On Merlin, Pentium D. Upgraded pupsave from 264 to 265 seemingly without incident. HardInfo report at http://www.jades.org/comps/hir_mer_luci265.html.
Will test XineDVD with a couple of DVDs later on if I remember.
Will test XineDVD with a couple of DVDs later on if I remember.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Testing
playdayz
No apologies necessary. You have heaps on your plate as it is. Thanks for taking the trouble to put me right.
It was good to have confirmation that it wasn't something I was doing wrong nor a problem unique to me. 99% of the time that may very well be true but it is extremely discouraging to the noobish amongst us when that seems to be the default assumption by some. The only reason I test at all is that I believe that non-expert testing can be useful if the aim of puppy is still to produce a distro that is noob-friendly.
No apologies necessary. You have heaps on your plate as it is. Thanks for taking the trouble to put me right.
It was good to have confirmation that it wasn't something I was doing wrong nor a problem unique to me. 99% of the time that may very well be true but it is extremely discouraging to the noobish amongst us when that seems to be the default assumption by some. The only reason I test at all is that I believe that non-expert testing can be useful if the aim of puppy is still to produce a distro that is noob-friendly.