Puppy Linux Discussion Forum

NathanO · Joined: 22 Feb 2007 Posts: 198 Location: San Antonio, TX

Testing at the San Antonio Public Library WIFI. Took 3 reboots, four scans on this last reboot, and two auto DHCP to get the WIFI on this HP zv6000 laptop to stay 'on'. 3.01 never had this problem here.

Will test at San Antonio College tonight. I always have problems there.

NathanO

NathanO · Joined: 22 Feb 2007 Posts: 198 Location: San Antonio, TX

At San Antonio College, managed to get on WIFI with only three 'scan', 'choose', and two auto DHCP. There seems to be a problem with keeping the WIFI in this HP zv6000 laptop 'on' between scanning for a connection and doing the auto DHCP. Once it gets an IP address then it will stay on.

This was not a problem with 3.01.

NathanO

nic2109

WhoDo · Posted: Mon 03 Mar 2008, 03:40 Post subject:

AJ, to avoid confusion with later versions, would you mind renaming this thread as Puppy 3 Series Bugs? I know you don't have to, but it would be helpful.

Thank you.

alienjeff · Joined: 08 Jul 2006 Posts: 2291 Location: Winsted, CT - USA

Hi Warren.

The title is version, state and state-number specific. It was chosen with the express interest of avoiding confusion.

"Puppy 3 Series" is a rather broad umbrella, at least IMO. It covers:

3.00alpha(s)
3.00beta(s)
3.00 final
3.00retro
3.00 fat free
3.01alpha(s)
3.01beta(s)
3.01 final
3.01retro
3.01 fat free
3.01-NOP
3.01-NOP-rev1
Chihuahua(s)
DCL
Fire Hydrant Featherweight 3.0b
Fire Hydrant FHmainAbi3.0b
Fire Hydrant FMmainOoffice3.0b
Fire Hydrant Inferno3.0b
Fire Hydrant FH_Jwm3.01c
Lassie(s)
LighthousePup 3.01a4
LighthousePup 3.01a4oo2.2
Pupeee
Shard 3.01
Talking Stick(s)

... and perhaps more, but I've run out of time and interest in hunting them down.

I'll be more than happy to change the topic to your choice, however in light of the above, I'd appreciate an explanation of how it will avoid confusion. And please forgive me if I'm missing something obvious here.

wingruntled · Joined: 20 Feb 2007 Posts: 287 Location: Great Lakes

I can see aj's point.
But maybe v3.02alpha* bugs would trim things down a bit.

urban soul · Posted: Fri 07 Mar 2008, 12:54 Post subject:

I found a little bug in the network wizard in wag-profiles.sh in the function loadProfileData() :
This prevents the AP_MAC variable from beeing stored correctly.

WhoDo · Posted: Fri 07 Mar 2008, 19:00 Post subject:

alienjeff · Joined: 08 Jul 2006 Posts: 2291 Location: Winsted, CT - USA

What I'm taking issue with is maintaining subject clarity. My motives are honorable. I assure you it's not my well-known defiant streak rearing it's ugly head. Besides, if I wanted to really pick at nits, I would have said that using the word "Puppy" in the subject is unnecessary.

I remain unconvinced, but am open for further discussion.

WhoDo · Posted: Fri 07 Mar 2008, 23:10 Post subject:

alienjeff · Joined: 08 Jul 2006 Posts: 2291 Location: Winsted, CT - USA

prehistoric · Joined: 23 Oct 2007 Posts: 1337

I just changed the way my test system is installed. While everything works, the way options are presented is bound to confuse newbies. I had a frugal install on a flash drive, and I still have a frugal install there. What has changed is that the system now boots from there instead of from CD. People would report all these configurations as frugal installs:

1) pup_save.2fs or pup_save.3fs (only) on flash drive, boots from CD
2) above, plus sfs files on flash drive, boots from CD
3) bootable installation on flash drive with USBFLASH, syslinux, vmlinuz, initrd.gz and above.

Depending on the space available on the flash drive, each alternative can make sense in some circumstances.

When the installer found the pup_save.2fs file on a mounted drive, it gave me a message talking about a pup_save.3fs file. When it explained the options for solving the problem I didn't see the one I used, reboot with "pfix=ram", so it will ignore the pup_save.2fs file, do a typical frugal install to flash drive, choose "do not save" on shutdown. On reboot the system comes up using the previously created pup_save.2fs file. There is no confusing renaming, and no need to boot another system.

It is very likely more and more people will be using flash drives with preexisting pup_save files. (I'm out of empty flash drives. All are in use testing something.) We need to handle this better.

There is also the minor irritation of being asked about copying sfs files that were just installed. This is mostly harmless, but another source of confusion. ("Did I or did I not install these?")
---------Firefox "minefield"
This beta keeps trying to install the DOM inspector and then discovering it is incompatible, forcing an uninstall and restart. I thought I turned updating off, but it did it again. Anyone else experiencing this?

---------Xorg and modelines
Ages ago, by Puppy standards, I rashly told AJ I could solve his i810 video problem. All my experiments with systems having Xorg 7.2 failed to accept a modeline. This has been my secret weapon for getting video working whenever one Linux system was able to use video, but another was not. Can somebody explain what happened to modelines? I haven't seen anything elsewhere stating that these are no longer allowed, yet it seems Xorg is overriding an explicit modeline which is demonstrably within the range of the video adapter and monitor.

BTW: after years in which scarcely a week went by without a call to do something on a machine using one of the i810 chip sets I have now been two months without finding one I could use to reproduce AJs problem.

prehistoric

WhoDo · Posted: Thu 13 Mar 2008, 21:43 Post subject:

BarryK · Posted: Thu 13 Mar 2008, 22:33 Post subject:

urban soul · Posted: Mon 17 Mar 2008, 21:58 Post subject:

Will have a look at it till friday.
Urban