I don't have access to my two laptops with bcm43xx on them, so I can't try them with the new (older) kernel. I just have my Nokia N800 handheld computer. I am running the newest Dingo (older kernel ) alpha 6 on a modern Gateway desktop computer, and it looks great. No problems thus far.

Up/down keys by trackpad work, never worked on 3.01 and earlier. Makes navigating some web pages much easier.

Tried BBC radio (I'm a Brit), radio sounded OK but then cut off after 1 min 20 sec or so, tried again and cut off after approx same time. Tried open in standalone player, got very broken sound, and same cut off time.

Ripoff MP3 rippper seemed very slow, but I'd never used it before, maybe operator error.

Pdf viwer started OK and opened files, but just shut down with no warning if down arrow or page down was used. Repeated with same effect several time. Same/similar pdf viewer in Puppy3.01 (didn't actually check which versions) works fine.

Battery monitor seems to be black on dark grey, no actual %, reported in another thread.

In general, seems quite quick, maybe slightly quicker than other Puppies, a bit too orange for my taste (not worked out how to change that as theme doesn't seem to affect it), generally usable, but would be nice to get the main issues sorted.

On the "stay at home" (ZPC-9000) system, my script using the iwpriv commands works and allows me to connect to my wpa2 network. However, my scrpt using wpa_supplicant fails due to lack of RALINK driver support. Trying the network wizard, if also fails. From the appearance of the "blinky" network lights, I suspect it also has wpa_supplicant problem. The wpa_supplicant version is 0.6.0.

On the Eee PC, I have no luck with the ath_pci driver. There is no creation of ath0 interface. The interesting thing is I can turn on or off the card with
Function F2 key, but, still no interface. I have used Raffy's breezy and can connect.

I still get the "unsafe /tmp permissions" error with syslinux on USB installations.

I think going back to the older kernel is not solution. The problem is the kernel modules for the wireless hardware. Having a wpa_supplicant that supports the RALINK and wifi drivers would help. I think the ath0 problem may be a module dependency issue. I will check my notes, I seem to have encounter this with ath_pci driver before._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

Hi all,
yes I did the d/l, checksum, and burn cd. The developers
blog said the linkback was to the puppy version with kernel
K 2.6.21.7 but I found the linkback was to the version with the
kernel K2.6.23.12 ! So still no forward or back as the case maybe.

I didn't mention this before, but Dingo is looking very good. Seems quite fast.

I've tried it on 2 laptops and 4 desktops (3 with ide, 1 with ide & sata) without problems, except for the bcm43xx on my wife's laptop. That's nothing new though. It's been hit or miss with the bcm43xx for a while. That wireless card has two different kernel modules it could use and two different sets of firmware depending on how old the card is.

The rt2x00 drivers for Ralink have been buggy for quite a while, perhaps now that they're main-lined they'll improve. The legacy Ralink drivers are quite stable.

Probably by the time Dingo gets to beta 2.6.24.1 will be out with a truck load of fixes. Keep pressing foward!

my scrpt using wpa_supplicant fails due to lack of RALINK driver support.

Barry, I recommend reverting to the older 0.5.8 version of wpa_supplicant, patched for Ralink support. I compiled and packaged this version during Puppy4's early stages -
http://www.murga-linux.com/puppy/viewtopic.php?p=151956#151956
wpa-supplicant-0.6.0 was supposed to support Ralink out of the box, but it clearly doesn't work.

JustGreg wrote:

On the Eee PC, I have no luck with the ath_pci driver.

That's to be expected. The standard ath_pci driver does not support the particular Atheros chipset in the Eee.
Once Puppy4 is finalised we will need to compile the special patched version of the ath_pci driver for you ... but this driver will need to be installed as an add-on, because it breaks compatibility with other Atheros wifi devices.

Thanks for putting in the battery monitor. In order to see the whole battery monitor, /root/.jwmrc-tray line 2 height="26" should be changed to height="28".

Also, The File-Sharing (Pcurlftp) Rox app depends on pure-ftpd. I think you said you were going to include it. Anyway pure-ftpd is a pet package available on Pet-get, but the package has a problem. The folder /root/ftpd needs to have its owner changed to ftp and permissions set to 777 or 755.

Some folks said they had problems with bcm43 wireless. My wife's laptop has a bcm43. It didn't get the module loaded. I ended up having to rmmod the b43 and ssb modules and then modprobe the bcm43xx. If I can get some more time with her laptop I'll try to figure out what's going on.

I have fixed the tray height.
I changed /root/ftpd owner to 'ftp'.
I have now included pure_ftpd.
Note, the PET package is named 'file_sharing-curlftpfs-mpscan-0.1-0.9.1-0.1.0'.

The fixes did not make it into the alpha6 build with 2.6.21.7 kernel nor the 3.02alpha1.

This annoys me a lot.
A password field lenght issue.
See: http://www.murga-linux.com/puppy/viewtopic.php?p=170856#170856

I would appreciate a solution.

I've used gFTP for years, never run into a problem with password size.
I think, from memory, the biggest password I have used is 10 characters.
The problem is more likely to be the ftp server at the other end._________________http://bkhome.org/news/

This annoys me a lot.
A password field lenght issue.
See: http://www.murga-linux.com/puppy/viewtopic.php?p=170856#170856

I would appreciate a solution.

I've used gFTP for years, never run into a problem with password size.
I think, from memory, the biggest password I have used is 10 characters.
The problem is more likely to be the ftp server at the other end.

The problem is I can't enter a password bigger then 7 characters in the gui field of gFTP. No problem to enter a userid bigger then 7 characters.

It's not a question of a problem at the server end as I can go to it with FileZilla in Windows without a problem.

EDIT
I tried in 3.01 with gFTP at 2.0.18, same problem.
As I had FileZilla in 3.01 installed also I tried and I have no problem to connect to my website.
So definitely a problem in gFTP._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum