(old)Puppy Linux Discussion Forum

tempestuous wrote:

rokky wrote:Interesting, too that the no WPA support message would pop up when the wifi card is not even detected/known...

The WPA warning only appears when the user selects "WPA" or "WPA2" encryption, and a non-WPA-supported wifi module has been selected.

Hello tempestuous,

thank you for the input on the -D param for wpa_supplicant in your previous post!
The warning pops up when wag-profiles.sh is run and the command
`readlink /sys/class/net/$INTERFACE/device/driver`
does not return one of these:
'hostap | rt61 | rt73 | rt2500 | bcm43xx | ipw2100 | ipw2200 | ipw3945 | r8180 | r8187 '

This is also true if no driver was loaded or the interface is unknown to puppy.

Additionaly the WPA fields are disabled. The list above is beeing updated for the final release if I understood right.
If we need a database for the wireless drivers how about putting it in a separate file (with an update function) ? /etc/networkmodules could be used e.g.

Urban

Edit: in Dingo 4.00 final puppy knows about these drivers supporting WPA:

hostap
rt61|rt73
bcm43xx|ipw2100|ipw2200|ipw3945|ath_pci
ndiswrapper
zd1211|zd1211b|zd1211rw|ath5k|b43|b43legacy
iwl3945|iwl4965|rndis_wlan|rt61pci|rt73usb
r8180|r8187|rtl8180|rtl8187

hope this is of interest for regular users.

Urban, you have raised two separate issues:

urban soul wrote:If we need a database for the wireless drivers how about putting it in a separate file (with an update function) ?

That's for Barry and/or rarsa and/or Dougal to decide. I just contributed some configuration details. Scripting was done by rarsa, then modified by Dougal for additional features.

urban soul wrote:The warning pops up when wag-profiles.sh is run and the command
`readlink /sys/class/net/$INTERFACE/device/driver`
does not return one of these:
'hostap | rt61 | rt73 | rt2500 | bcm43xx | ipw2100 | ipw2200 | ipw3945 | r8180 | r8187 '

This is also true if no driver was loaded or the interface is unknown to puppy.

I was about to suggest that the WPA warning in this instance is erroneous and should be corrected ... but then, I don't really see a fault. If no interface is selected, then certainly WPA is not possible! Maybe it's just the wording of the warning that needs to be changed?
Or if we look deeper, I'm wondering whether the fault is further back in the chain? Perhaps the Wizard should not even allow a user to get to the wifi configuration gui if no module is selected?
Again, ultimately this is not my decision. Feel free to move this information to a new thread in "Suggestions".

Personally, I would like to see Pwifiscan (or whatever it's called) integrated into the Network Wizard.

Follow up on HP Pavilion zv6000 per Barry's request.

Cold Boot
.25 Kernel lsmod:
usbhid 31616 0

I will have to hand copy the devices file with spaces as on the laptop screen:

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 pd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sun=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 2.06
S: Manufacturer=Linux 2.6.25 ehic_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:13.2
C:* #Ifs= 1 Cfg#= 1 Atr=e) MxPwr= 0mA
I:* If#= 0 Alt=0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

Cold Boot
.21 Kernel lsmod:
usbhid 24928 0

Copy of device:

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.21.7 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:13.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 4
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.21.7 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:13.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 4
B: Alloc= 14/900 us ( 2%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.21.7 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:13.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=1241 ProdID=1166 Rev= 2.70
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms

Anything else you need?

Hello All,

I booted up dingo final and installed it fresh full/wipe drive.
When I try to reboot I get an error that kernel panic filesystem not syncing, can't mount VFS and then something from grub perhaps about block device (0,0) which is the correct hard drive and partition where puppy and grub were installed.

The puppy .25 kernel version worked fine and all previous versions of Puppy, but not dingo final release .21.7 kernel version. I do not wish to use the .25 version because the wireless setup in the network wizard has new drivers that don't work with my dlink wireless pci card., the old ath0 driver in the dingo release candidates worked fine.

Thats my sad but true story.

Mny Thx,
Vito
AMD 750 box with 356 mb memory

Hi Barry.
Just tried Final of 4.0 and get same result as the SC version

2.6.25 Kernel, MD5 sum correct. disk verified on blowing. Intel D201GLY2 MB

Stops at booting linux kernel.

Previous version of 4 with later kernel have worked so not sure what has changed.

This CD works fine on an older Athlon.
Cheers
Tony

Hi Lobster et al,

Dingo4 Final is ready here

http://www.puppylinux.ca/puppyfiles/pup ... monkey.iso
http://www.puppylinux.ca/puppyfiles/pup ... so.md5.txt

The unleashed and devx will come soon....
Best,
Eric

Just been taking Dingo for a test drive - and very nice it is.

I noticed an uninvited guest in the CUPS printers screen - a printer (Brother model) there. Since I have never owned one of these models, it must belong to Barry. Must have crept in to the ISO via a CUPS configuration file somewhere.

The Xorg.conf file could've been edited and the tap option (for laptop touchpads) already set by default, as not doing this could turn away people (as rightly pointed by alienjeff in the other thread. ) How about doing that in upgraded version ?
The other thread : http://www.murga-linux.com/puppy/viewtopic.php?t=28724

Hi - an interesting event in the final on the latest kernel. The original boot from CD takes a very long time - at least 3 times the .21 kernel version, and fails to detect the USB mouse, HOWEVER, after a full HD install and reboot, the mouse is working I noticed this in the SC version also.

This version seems rather better with my ZD1211rw wireless dongle. Network Wizard still fails to set it up, but Pwireless has no problems.

Barrie

Also, on my baby laptop, the rxvt terminal display is frequently messed up :

full hard disk install on dell gx240

using 2.6.21.7 kernel selecting poweroff, the machine powers off fully

using 2.6.25 kernel selecting poweroff, the system halts and the disk(s) seems to powerdown but the whole machine keeps running

Sometimes the pin-board is missing, sometimes the ethernet card isn't detected, often when I click on an icon, the pin-board disappears.

I have 373 MB free on a CD-Live boot. The earlier 4.00 alpha and beta 1 worked well, but not beta2.

When I finally boot and everything "catches" and loads, it seems ok, but I have to boot several times - or be very lucky.

Did the kernel change between the early 4.00alphas? 3.01 works find and all earlier versions.

This 4.00 looks wonderful. But it is frustrating to have to boot into it several times!

The disk icons aren't showing as they were with beta1 but I think this is user selectable.

I don't want to make it work as 4.00 is up and running (so far) and I don't want it to crash.

In the earlier attempts to boot, I got "segmentation fault" on the command line after X crashed.

I hope this is helpful to someone.

Best to all,

David

Further to my posting above.

When I run things like gftp from the command line, the program crashes and says "segmentation fault".

I checked the md5sum of the iso and used "Burn ISO 2 CD" and verified the burn as "good".

I hope this is helpful.

Thanks

David

Oh, I am running an AMD Athlon 1400 with 1 GB memory. Running 4.00 from a CD in RAM. The computer is about 9 years old now - all previous Puppy versions up until 4.00 alphas worked ok, beta 1 was "so so" and beta 2 and "SC" had similar problems.

Best

David

Hi all,

using a frugal install of 4.00 final I noticed that the password that I enter when mounting a personal save file (with heavy encryption created with Puppy 3.01 or 3.00) is being shown as plain text, while it was not shown at all with 3.01.
I confirmed this behavior by choosing "none" when booting 4.00, creating a small h.e. save file when shutting down, then choosing this save file when rebooting - password was again shown in plain text.
I have not yet tried with light or no encryption.
Am I doing something wrong, is this a bug or a feature ?
(Or have I missed an already existing posting about this ? A search did not turn up anything for me ...)

In general, though, the new release looks good to me and I look forward to giving it a more detailed try.

I just found out that some of my private wireless profiles made it into the default config file for Puppy 4.00! Wow!

The problem is not that if you happen to be at Berlin, Alexanderplatz every Puppy-Linux-User can surf the internet (profile: "alex") . No - - - the problem is, that one of these profiles has a wrong line count. This will prevent the network wizard from working correctly. So please replace your file /etc/WAG/profile-conf with the version provided as a attachment.

Happy surfing!
Urban

paulh177,

I get exactly the behavior you describe - always - on 3.01 and all the
Dingos. A full shutdown except for the final power off.

paulh177 wrote:full hard disk install on dell gx240

using 2.6.21.7 kernel selecting poweroff, the machine powers off fully

using 2.6.25 kernel selecting poweroff, the system halts and the disk(s) seems to powerdown but the whole machine keeps running

If I use acpi=force boot parameter, I get a full shutdown.

However, for me, on all the older pups acpi=force causes strange
side effects. It causes intermittent boot lockups at a variety of points
in the boot process; and sometimes I get a strangely twisted mouse
where I expect the mouse to go up the screen and it goes to the
right instead. The twisted mouse can survive several bootups - even
cold off/on cycles.

Both sage and Dougal assure me that these are hardware problems,
but the fact remains that I never see them unless I use acpi=force.

So, I press the power button after I see the Power Down message.

Try acpi=force - it will most likely give you a full shutdown and may
not have any side effects for you.

I haven't yet tested this extensively on the .25 kernel - maybe my
problems will go away.

Good Luck,

GeoW

GeoW wrote:paulh177,
I get exactly the behavior you describe - always - on 3.01 and all the
Dingos. A full shutdown except for the final power off.

Interesting. I've never had this behaviour before on this particular piece of kit and I've run a few different Puppies (2.x, 3.x & now 4.x) on it. It is quite specific to Dingo and the newest kernel

(AAMOI I do get the same thing on however an old laptop running 2.15 -- I just assumed it was a laptop vagary. Never experimented with acpi etc on that machine however)

paul

The new ALSA wizard doesn't detect my PCI SoundBlaster Live! card while previous versions did. Of course everything is so intermittant with my computer running Puppy 4.00 that this might be just peculiar to me.

Be well,

David

I followed Tempestuous advice and look at the readme file for RT73usb driver. The information is available from http://rt2x00.serialmonkey.com, one needs to search the site for "rt73usb". Only information on iwconfig is given to configure the device. Unfortunately, "iwconfig" can only be used to setup WEP for security. I checked Dingo Kernel 2.6.25 if the rt73usb module supported "iwpriv" commands, which would allow one to setup a WPA connection. However, there is no iwpriv functions supported. The use of WPA with this driver is a future development.

I also checked the ralink website. There is a driver for the rt73 hardware, which supports kernel versions 2.4 and 2.6. The driver was released in Januray 2008 so it should support the latest 2.6 kernel. It does need the Wireless Extensions V18. It supports iwpriv commands and the use of wpa_supplicant. I have attached the January 2008 ralink driver for anyone's use. For the newbies, package needs to compiled before one can use it. Hopefully, this will help with Dingo Kernel 2.6.25 development.