I did an installation of alpha 5 to a vfat USB flash drive and here is what I found:

First boot failed with statement of boot failure. I checked and found that ldlinux.sys was not installed. The problem is from syslinux-nomtools. When one runs syslinux-nomtools, an error message of "prossibly unsafe /tmp/permissions". I used syslinux under Puppy 3.01 and ldlinuxsys was installed. The usb device booted correctly in Dingo alpha 5.

Second is wpa_supplicant version 0.6.0 does not support the RALINK drivers. Solution is to copy wpa_supplicant (version 0.5. from Puppy 3.01 to the directory /user/sbin over the existing wpa-supplicant.

Other than those two, Dingo alpha5 is working nice. I am using it to write this. I have changed the desk top to get the yellow or gold out._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

Testing 395 on an IBM Thinkpad T61 with iwl4965 wireless.
Seems to require mac80211 before it will associate with an AP.
Then get many reports of:

Quote:

RX non-WEP frame, but expected encryption

This latter has also been reported in Ubuntu forums, but solution seems elusive.
Then tried D-Link DWL-650+ with the acx module. It reported that the firmware is not present. (recurrence of an old problem).
Ndiswrapper works okay however. Currently posting from wireless using ndiswrapper.
[/b]

I did an installation of alpha 5 to a vfat USB flash drive and here is what I found:

First boot failed with statement of boot failure. I checked and found that ldlinux.sys was not installed. The problem is from syslinux-nomtools. When one runs syslinux-nomtools, an error message of "prossibly unsafe /tmp/permissions". I used syslinux under Puppy 3.01 and ldlinuxsys was installed. The usb device booted correctly in Dingo alpha 5.

I have just tested a usb flash install using the Universal Installer.
I firstly deleted all files in the flash drive partition, unmounted, then ran the Uni Installer. It worked, ldlinux.sys got installed. It booted up fine._________________http://bkhome.org/news/

Until 1.07, the live CD booted with no problem
Until 3.01, and dingo alpha 1/2 (?) the CD booted with boot-parameter "ide1=0x180"

With Alpha 5 it doesn't boot at all on this machine. Tried all combinations with "nopcmcia", "ide2=0x180" etc which work for Slackware-based distros. The error is, that after loading the initrd (this still works), the system can't find the (external) CD ROM and jumps to an emergency shell...

Is there a new parameter available - or could be the PCMCIA stuff is suddenly missing in the kernel at this alpha stage....?

Dingo has introduced the wireless module ipl3945 in the place of ipw3945. This module lacks WPA support, which makes wireless networking a "No Go" for me and many others.

Is there an alternative module for the Intel/PRO 3945 wireless lan card? I got several false hits when trying to Auto-load but found nothing that worked.

BTW, WPA is supposed to be present in 3.01 but fails for me and I had to go back to 2.16 to find one that worked. It still uses ipw3945 so there's something else getting in the way in the younger puppies.

Edit (days and days later) - I've discovered since the above post that while the Network wizard says that the WPA connection could not be established and returns with a "Failure" message, that it then retries and eventually works. Well it did in Muppy008, where it has worked reliably since then. So I conclude that it's ONLY Dingo that has a WPA problem, and that is by design thanks to the choice of module i.e. ipl3945 in place of ipw3945. Last edited by nic2109 on Sat 19 Jan 2008, 18:09; edited 1 time in total

I am using a wireless USB dongle (Zydas 1211b chipset) with WPA. Go through the network setup and it comes back saying it has connected. I then open the web browser and it hasn't in fact connected but about 20 seconds later there is activity from the cd and then it connects fine.

The move to Xine is great especially in the browser. One issue, on some radio streams it come back MMS is not a registered protocol.

I have just installed net_setup-3.96 pet on Puppy 3.01 system with Linksys USB wireless device (RT73 driver). It solved the problem with network wizard connecting to a WPA2 network. I no longer need the script using wpa_supplicant that I have been using. I defined the profile and it works.

I know this is the same version in Dingo alpha 5. I gave it a try. Previously I reported that my wpa_supplicant script failed with the wpa_supplicant in alpha 5. I was surprised to see the network setup script report it could not make the WPA connection. Then the script ran a test of wireless network and the connection was made. I hit the autodhcpc key and could use the network. I do not completely understand what is going on. The new network setup script does work for me, a bit strangely in Dingo alpha 5.

I found the problem I had installed version 0.5.8 for wpa_supplicant, wpa_cli and wpa_passphase. I need to restore the correct version. I restore the correct version and now can not connect to WPA2. The new version of wpa_supplicant (0.6.0) does not support the RALINK drivers._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love MuchLast edited by JustGreg on Sun 13 Jan 2008, 21:42; edited 1 time in total

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