Will,HairyWill wrote:Clicking on various text files in rox fails launches error message about vi: NOT FIXED
Using vi from the console opens the file successfully in e3 in the correct mode. Clicking on the file opens an empty terminal window with a title vi that does seem to respond to any of the weird key combinations I can think of. Would it not be sensible to replace this with a shell script /bin/vior am I missing something?Code: Select all
#!/bin/sh e3vi "$@"
Ok, I've improved the naming for HotPup in the menu.HairyWill wrote:
comments:
Seeing that HotPup is disabled by default it might be sensible to give the menu entry a (marginally) less cryptic name such as "HotPup disk automounter"
It would be nice to include buttons for Autoconnect and Pwireless in the dialog launched from the Connect icon on the desktop. Because it is at the top of the menu I suspect that newbies will try Autoconnect before Pwireless. This would be a sensible choice in an area populated by open networks. Around me most networks use encryption and some are open but with MAC filtering. In this environment the best choice to make your first connection is probably Pwireless.
The volume trayapp version used doesn't, in my experience, use any less resources when idle than the 0.8 version which is more functional and looks better. If you sit there wacking the slider up and down then the included version does use less cpu (I don't use my volume control like that). The minimal-0.9 version in the package manager gives a 404 when attempting to download. This version is functionally different from the others and requires a jwm traybutton to launch it. Unless the installer inserts one of these into the tray I think this version should not be put in the repository as it will probably just confuse people.
I put a fair bit of effort into these. I don't mind which version is in the final release, but being objective I don't think Barry has made the best choice.
I don't think that any of these are show stoppers.
Actually, it says a missing "xvid" -- but that's a false alarm. That is an incorrect dependency in the packages.txt file. I've fixed it.ttuuxxx wrote:But then I installed mplayer via petget and it had a missing "divx" file, doesn't say which version or anything useful. So i figure the mplayer full codec pack should fix that, nope still missing "divx" so I figured why not just try mplayer, so I click the icon and it 2 boxes came up, 1 black and 1 white. Then my pc froze, which it never does and I had to press ctrl+Backspace to exitx and then startx to get back,
That memtest has been there for a long time. I never use it. Maybe it needs to be looked at, perhaps constrained to only run if X isn't. Anyway, I have removed it from the default selection.dogone wrote:Either I'm missing something or Memtestshell is terribly dangerous under X.
Memtest has never worked for me under X and running it from Puppy's menu ALWAYS locks up X, requiring a system hardware reset. If others are experiencing this problem, Memtestshell should be fixed or removed from the menu and implemented outside of X.
It may be necessary to treat your computer as a special case.mbe wrote:Boot from frugal install was fine but I still I needed to modprobe yenta_socket to get the USB2 and wireless interfaces on PCMCIA cards to appear. WPA/TKIP configured perfectly using the wireless wizard with ndiswrapper. I added modprobe yenta_socket to /etc/rc.d/rc.local as a workaround. - Shutdown offered a save file and the interface appeared nicely on a reboot - would it be possible to add the modprobe yent_socket line to one of the startup scripts in initrd for 4.0 final ?
Ah, you're one step ahead of me. Rerwin and mbe, you must have already been through this exercise somewhere else in the forum.rerwin wrote:mbe,
I think the solution is to add an override entry for your cardbus controller into /etc/rc.d/MODULESCONFIG. Insert the following line after line 21, just before the line consisting of a single tick-mark:Please report whether this works, so we can advocate its inclusion in the final. Thanks.Code: Select all
yenta-socket 0x00001217 0x00006933 #O2 Micro, Inc. CardBus/SmartCardBus Controller v4.00
Richard
Ahem, I should read ahead before posting!mbe wrote:Richard
Excellent result - I removed my extra line from /etc/rc.d/rc.local and added your line into /etc/rc.d/MODULESCONFIG then rebooted - the cards came up straight away and the wizard auto-connected via nidiswapper with WPA/TKIP since it was already configured from before.
This is clearly a better fix for me but does it need to be so hardware specific ?
Thanks a lot
Martin
With the .25 kernel, the bcm43xx module is replaced by b43 and b43legacy modules.geneven wrote:I had two problems with the (625?) kernel.
One, the correct module for my BCM43xx wireless didn't load and didn't appear to be available. So my usual tricks for getting on the internet didn't work. This does NOT happen with the other Puppy posted today. (621?)
Two, there is something strange about the combo method for installing on my 2 gig USB stick. This happens with BOTH Puppies posted today.
When I first boot into one of the new Puppies, I have about 500 megs of free space, which is usual. But after I reboot and select the default location for creating a personal storage file, I have about 30 megs. I started with 2 gigs, so it' seems that the wrong partition is being selected for the personal storage file?
Incidentally, another thing is that I don't get any appropriate error messages. When I go to create, say, a 512 meg storage file after being told that I have about 30 megs free, the system lets me ask for 512 megs that don't exist. Then, when I reboot, I don't get an error message even though the 512 meg file can't be created. Seems to me that I should.
I'm also running Dingo with k2.6.21.7. I plugged in an SD card, ran Pmount, there it is, mounts ok.capoverde wrote:Running Puppy 4 Dingo k2.6.21.7:
surprise, a plugged SD card isn't detected, no matter what way (HotPup, PMount or MUT); no use restarting X or inserting the card before power-up.
?!? - Previous Puppies, including Dingo Alphas &Betas, had no problems at that -- MD5sum checked OK. Will try on other machines, with an external card reader.
One of the contributors to the Network Wizard has put that code in that puts up a message about WPA not being supported ...but, how to know that?JustGreg wrote:I have tried a frugal installation of Dingo with kernel 2.6.21.7 and everything worked fine. No problems were encountered. I have downloaded Dingo with kernel 2.6.25 with a frugal installation and tried to connect to my wireless device (driver rt73USB). Using the connection wizard, I surprised to see the message that the rt73USB driver does not support WPA. This is probably a driver problem. The same problem was encountered with kernel 2.6.24 (dingo 3.96, I think). Is it possible to use older version of rt73usb driver (one used with 2.6.21.7) with the newer kernel? This will be a problem also for the Intel Classmate. The Intel Classmate wireless device also uses the rt73usb driver. Thank you in advance for any help on this one.
Code: Select all
# Dougal: find driver and set WPA driver from it
INTMODULE=`readlink /sys/class/net/$INTERFACE/device/driver`
INTMODULE=${INTMODULE##*/}
case "$INTMODULE" in
hostap*) PROFILE_WPA_DRV="hostap" ;;
rt61|rt73) PROFILE_WPA_DRV="ralink" ;;
bcm43xx|ipw2100|ipw2200|ipw3945|ath_pci|ndiswrapper|zd1211|zd1211b|zd1211rw) PROFILE_WPA_DRV="wext" ;;
r8180|r8187) PROFILE_WPA_DRV="ipw" ;;
*) # doesn't support WPA encryption
Xdialog --wrap --title "Wireless interface configuration" --msgbox "Note: The interface you have selected uses the module $INTMODULE,\nwhich does not support WPA encryption." 0 0
PROFILE_WPA_DRV="" ;;
esac
You are the second person reporting this problem. I have a suspicion that the problem experienced with the .23/.24 kernels and usb has re-emerged.NathanO wrote:Tested both versions. Older kernel works ok on both the tower and the laptop.
6.25 kernel ok on the tower, would not work with USB mouse on the HP Pavilion zv6000 laptop. This is the first version of Puppy that I have run into this problem on. What information would you need to find the problem?