Wary Release Candidate (104) feedback

Message

rjbrewer · #41 Post by **rjbrewer** » Fri 24 Dec 2010, 00:07

BarryK wrote:
rjbrewer wrote:Still needs this fix to make rox-clicking work right;

http://murga-linux.com/puppy/viewtopic. ... 682#468682
I don't want to implement that fix.

I did try it and got errors in Rox, windows freezing. I have also read that this "fix" can cause trouble.

So, I have to put this one on hold for now.

After Wary Final is out, I will get onto the Rox developers to see if it can get fixed finally -- it was only partly fixed before.

I'll refer to it as a "temporary workaround" instead of "fix".

Your Melbourne holiday photos are great!
Happy Holidays!

CHLee · #42 Post by **CHLee** » Fri 24 Dec 2010, 00:45

Hi Barry,
I have two different USB wi-fi , zd1211rw (old) and rtl8187(new buy). They both could not connect my AP (WEP) in the Wary with kernel 2.6.31.14.
I tested both USB wi-fi with different kernel 2.6.30.5, 2.6.33.2, ... in Wary/Quirky/Puppy, they work very good.
When dmesg, I found "wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate", is it have any different in kernel 2.6.31.14 .config ?
Hope tempestuous have some idea.
Thanks,
CHLee

zd1211rw:

Code: Select all

usb 1-2: new high speed USB device using ehci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
usb 1-2: reset high speed USB device using ehci_hcd and address 2
phy0: Selected rate control algorithm 'minstrel'
zd1211rw 1-2:1.0: phy0
usbcore: registered new interface driver zd1211rw
usb 1-2: firmware: requesting zd1211/zd1211b_ub
usb 1-2: firmware: requesting zd1211/zd1211b_uphr
zd1211rw 1-2:1.0: firmware version 4725
zd1211rw 1-2:1.0: zd1211b chip 0ace:1215 v4810 high 00-19-e0 UW2453_RF pa0 -7---
cfg80211: Calling CRDA for country: DE
wlan0: authenticate with AP 00:26:5a:43:eb:e4
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: authenticate with AP 00:26:5a:43:eb:e4
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: authenticate with AP 00:26:5a:43:eb:e4
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

rtl8187:

Code: Select all

usb 1-2: new high speed USB device using ehci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
phy0: Selected rate control algorithm 'minstrel'
phy0: hwaddr 08:10:74:b7:e3:54, RTL8187BvE V0 + rtl8225z2
rtl8187: Customer ID is 0x00
Registered led device: rtl8187-phy0::tx
Registered led device: rtl8187-phy0::rx
usbcore: registered new interface driver rtl8187
wlan0: authenticate with AP 00:26:5a:43:eb:e4
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: direct probe to AP 00:26:5a:43:eb:e4 try 1
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: authenticate with AP 00:26:5a:43:eb:e4
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

rcrsn51 · #43 Post by **rcrsn51** » Fri 24 Dec 2010, 01:27

BarryK wrote:
rcrsn51 wrote:There has been a slight change in USB behaviour with Wary 104. In previous Puppies/Quirkies, it didn't matter if my printer-scanner was turned on or off at boot time. Either way, it was properly detected.

With Wary 104, I get varying effects when the scanner is already on at boot up. With my Canon unit, "Loading drivers" produces the line of red dots. But the scanner is detected.

With my HP unit, it is not detected at all and requires an off/on.

I believe that other people have reported odd USB behaviours.
I can't think what has changed that would cause any difference from Wary 102 or earlier.

I did some more testing and I don't think that the problem is 102 versus 104. But it's definitely different than Quirky.

If I boot Quirky with two printer/scanner units powered up, it starts quickly and always detects both units. Lupu is also fine.

With Wary, it starts more slowly and detects only one unit or neither. After the units are restarted, both are detected.

Sage · #44 Post by **Sage** » Fri 24 Dec 2010, 07:26

you guys who have this problem, is it with 'vesa' or 'Xvesa' drivers

Xorg, SisMirage1, PointMousePlus.
It transforms SM from something I hate, but use, to utterly unacceptable. Not previously encountered. I am less certain of the origin, though, as Opera is also affected to a small degree, as reported. It is my view that releasing a new version like this would harm your reputation.

DaveS · #45 Post by **DaveS** » Fri 24 Dec 2010, 07:39

BarryK wrote:
DaveS wrote:Awful problems with seamonkey scroll delay and display splitting.... sorry!
I don't have any noticeable scrolling delay, using 'intel' Xorg driver.

So, you guys who have this problem, is it with 'vesa' or 'Xvesa' drivers?

Also, is it only with the this latest SeaMonkey 2.0.11? Wary 102 and earlier uses SM 2.0.7.

If it turns out to be a problem with SM 2.0.11 then I will do a quick fix and roll SM back. Then I can worry about a better fix after 5.0-final is out -- like the new beta version.

Barry, this site is the worst http://www.skiboardsonline.com/forums/index.php

Using Intel Xorg driver. Not XorgHigh, so no direct rendering. The problem does not show up using Seamonkey 21beta (latest) but I have to add dbus for that.

On a secondary note, cannot find any bugs in Gnumeric

Lucid has some problems with Gnumeric just now......

Billtoo · #46 Post by **Billtoo** » Fri 24 Dec 2010, 07:46

I did a frugal install of Wary 104rc on an older pc which has an ati
9200 video card in it.

I installed the MESA DRI driver and it's working well.
I installed the Google Earth pet from lucid puppy and got it working by adding
some missing libraries that I found at http://packages.ubuntu.com.

OpenGL
Vendor Tungsten Graphics, Inc.
Renderer Mesa DRI R200 20060602 AGP 8x x86/MMX+/3DNow!+/SSE2 TCL
Version 1.3 Mesa 6.5.2
Direct Rendering Yes

edit: the missing libs for Google Earth were:

libaudio2_1.9.2-3_i386.deb
libaudio-dev_1.9.2-3_i386.deb
libc6_2.12.1-0ubuntu8_i386.deb

I'd attach them to this message but the last one is almost 4mb so it's
too big to attach.

BarryK · #47 Post by **BarryK** » Fri 24 Dec 2010, 08:31

rcrsn51 wrote:
BarryK wrote:
rcrsn51 wrote:There has been a slight change in USB behaviour with Wary 104. In previous Puppies/Quirkies, it didn't matter if my printer-scanner was turned on or off at boot time. Either way, it was properly detected.

With Wary 104, I get varying effects when the scanner is already on at boot up. With my Canon unit, "Loading drivers" produces the line of red dots. But the scanner is detected.

With my HP unit, it is not detected at all and requires an off/on.

I believe that other people have reported odd USB behaviours.
I can't think what has changed that would cause any difference from Wary 102 or earlier.
I did some more testing and I don't think that the problem is 102 versus 104. But it's definitely different than Quirky.

If I boot Quirky with two printer/scanner units powered up, it starts quickly and always detects both units. Lupu is also fine.

With Wary, it starts more slowly and detects only one unit or neither. After the units are restarted, both are detected.

Maybe it's an issue with the 2.6.31.14 kernel. Perhaps when I release Wary, I should also build a less-wary Wary with a recent kernel, just as a plaything for comparison -- I was thinking of the 2.6.37 kernel.

gerry · #48 Post by **gerry** » Fri 24 Dec 2010, 12:31

Can't run 104 on my Acer Aspire One. I burnt the iso to a usb stick using Unetbootin on the XP machine. Plugged it into AA1, and it started to boot. It searched for Puppy files, even telling me that it was searching sub-sub partitions (? Could have been directories). Eventually it gave up, saying:

"Boot partition not found. Dropping out to initial-ramdisk console...
/bin/sh: can't access tty: job control turned off"

iso is ok, it is same one I used to make live cd for old computer.

Unetbootin has worked many times before.

Is Wary looking in the usb stick for boot partition? Checked boot flag is set.

Gerry

smokey01 · #49 Post by **smokey01** » Fri 24 Dec 2010, 12:56

gerry, try this

http://www.smokey01.com/grant/Puppy%20o ... Drive.mpeg

rcrsn51 · #50 Post by **rcrsn51** » Fri 24 Dec 2010, 14:02

BarryK wrote:Maybe it's an issue with the 2.6.31.14 kernel. Perhaps when I release Wary, I should also build a less-wary Wary with a recent kernel, just as a plaything for comparison -- I was thinking of the 2.6.37 kernel.

I did some more testing this morning with Wary 104 and the problem wasn't as pervasive. Sometimes it would properly detect all the USB devices.So maybe it's not a major issue.

I then tried Wary 090 for comparison and it worked consistently. Could it have anything to do with the additional USB detection going on in 104 because of 3G modems?

rjbrewer · #51 Post by **rjbrewer** » Fri 24 Dec 2010, 15:31

I don't think it's a kernel issue.
With 098 it doesn't have any boot delay when usb or pcmcia are
inserted.
With 104 it does.
Same results with small or regular size 098 or 104.

gerry · #52 Post by **gerry** » Fri 24 Dec 2010, 17:42

I installed 104 onto a usb stick using the unversal installer, and plugged it into my Acer Aspire One. Hit two problems:

Could not get Xorg to run, so settled for Xvesa.

Once up and running, I tried to connect via wlan0, without success.

Both of these problems were reported as due to:

FATAL: could not load /lib/modules/2.6.31.14/modules.dep: no such file or directory.

Should it be there? Has something got lost along the way?
Or is Wary-104 not intended for netbooks?

Puppy 431 soldiers on.....

Gerry

BarryK · #53 Post by **BarryK** » Fri 24 Dec 2010, 22:35

gerry wrote:Can't run 104 on my Acer Aspire One. I burnt the iso to a usb stick using Unetbootin on the XP machine. Plugged it into AA1, and it started to boot. It searched for Puppy files, even telling me that it was searching sub-sub partitions (? Could have been directories). Eventually it gave up, saying:

"Boot partition not found. Dropping out to initial-ramdisk console...
/bin/sh: can't access tty: job control turned off"

iso is ok, it is same one I used to make live cd for old computer.

Unetbootin has worked many times before.

Is Wary looking in the usb stick for boot partition? Checked boot flag is set.

Gerry

Shinobar has reported this problem with Unetbootin to me, with a fix:

http://www.murga-linux.com/puppy/viewto ... 545#470545

I am not sure what to do about this. As Unetbootin copies isolinux.cfg to syslinux.cfg unchanged, it has 'pmedia=cd' which is wrong, it must be 'pmedia=usbflash'

Puppy was really working incorrectly before, allowing boot from usb Flash device when have 'pmedia=cd'.
The whole point of the 'pmedia' parameter is it says what media booting from.

I could reduce the "correctness" of the init script to get Unetbootin working, but I would rather syslinux.cfg is edited to be correct.
You can do it manually, or even better get the Unetbootin developer to put in the fix.

Alternatively, remove the 'pmedia' parameter entirely, it should work then, as the init script will default to searching everywhere for Puppy files.

BarryK · #54 Post by **BarryK** » Fri 24 Dec 2010, 22:46

rjbrewer wrote:I don't think it's a kernel issue.
With 098 it doesn't have any boot delay when usb or pcmcia are
inserted.
With 104 it does.
Same results with small or regular size 098 or 104.

The extra delay in 104 is deliberate, the init script waits a bit longer when usb drives are detected, to make sure all partitions are available. This actually should improve correct detection of all usb drives.

gerry · #55 Post by **gerry** » Fri 24 Dec 2010, 23:05

Barry- if Unetbootin is wrong, making a "wrong" in Puppy to match is not the answer (in my opinion).

Anyway, as I said above- Universal Installer worked, I think.

To install to a usb stick, I naturally went to "Bootflash- install Puppy to USB". But that told me that I should try Universal Installer first. I find that "intrigueing".

Gerry

rjbrewer · #56 Post by **rjbrewer** » Sat 25 Dec 2010, 00:55

gerry wrote:Barry- if Unetbootin is wrong, making a "wrong" in Puppy to match is not the answer (in my opinion).

Anyway, as I said above- Universal Installer worked, I think.

To install to a usb stick, I naturally went to "Bootflash- install Puppy to USB". But that told me that I should try Universal Installer first. I find that "intrigueing".

Gerry

Bootflash does not say that.
It gives you the option of installing immediately, or exiting and using
universal installer later.

Both methods work fine.

rjbrewer · #57 Post by **rjbrewer** » Sat 25 Dec 2010, 01:04

BarryK wrote:
rjbrewer wrote:I don't think it's a kernel issue.
With 098 it doesn't have any boot delay when usb or pcmcia are
inserted.
With 104 it does.
Same results with small or regular size 098 or 104.
The extra delay in 104 is deliberate, the init script waits a bit longer when usb drives are detected, to make sure all partitions are available. This actually should improve correct detection of all usb drives.

On my Dell 700m, both 098 and 104 will boot in 24 seconds
without any usb inserted.
I use a usb mouse; it slows 104 boot to 32 seconds while not
slowing 098 by more than a second.

Both versions show my 4 different flash drive devices without
problem.

shinobar · #58 Post by **shinobar** » Sat 25 Dec 2010, 01:13

BarryK wrote:Puppy was really working incorrectly before, allowing boot from usb Flash device when have 'pmedia=cd'.
The whole point of the 'pmedia' parameter is it says what media booting from.

I could reduce the "correctness" of the init script to get Unetbootin working, but I would rather syslinux.cfg is edited to be correct.
You can do it manually, or even better get the Unetbootin developer to put in the fix.

Alternatively, remove the 'pmedia' parameter entirely, it should work then, as the init script will default to searching everywhere for Puppy files.

Thanks for understanding.
Right, UNetBootin is wrong. But i think it is wise to keep backward compatible with reducing the "correctness" because it doesn't harm anything.
The init script automatically works assuming 'flash' for removable media even with 'pmedia=cd' option.

BTW, 'pmedia=usbhd' option seems not take effect with current init script.
No matter 'pmedia=usbflash' or 'pmedia=usbhd' makes the PUPMODE=13, doesn't it?

Q5sys · #59 Post by **Q5sys** » Sat 25 Dec 2010, 02:44

BarryK wrote:Maybe it's an issue with the 2.6.31.14 kernel. Perhaps when I release Wary, I should also build a less-wary Wary with a recent kernel, just as a plaything for comparison -- I was thinking of the 2.6.37 kernel.

Should be released as final within a week or two. I've been considering compiling it myself to tinker around with it... but I dont think I have the time right now with the holidays.

BarryK · #60 Post by **BarryK** » Sat 25 Dec 2010, 03:01

gerry wrote:FATAL: could not load /lib/modules/2.6.31.14/modules.dep: no such file or directory.

That is just plain weird. The first time that Wary 104 boots, 'depmod' runs which creates that file. I don't know any reason why that has not happened, it has never happened to me.

Anyway, if you open a terminal window and run 'depmod', that should fix it.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Wary Release Candidate (104) feedback

USB wi-fi

Wary Release Candidate (104) feedback

Unetbootin