Puppy 4 DINGO

Please post any bugs you have found
Message
Author
User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: Memtest test RAM fatal to X

#31 Post by BarryK »

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.
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.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: Yenta_socket does not load

#32 Post by BarryK »

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 ?
It may be necessary to treat your computer as a special case.

Run this in a terminal:

# grep -E '^i82092|^i82365|^tcic|^yenta_socket' /lib/modules/modules.pcimap.2.6.21.7

...does this give any output?

If yes, then the module should have loaded. If not, then we need to find what PCI vendor:chip IDs are your PCs PCI-to-PCMCIA interface, and associate those with the yenta_socket module.

Ok, go to the menu "Menu -> PupScan" and click on the PCI probe button, see if any of the entries is a Cardbus or PCMCIA interface -- if so, I need to know the vendor:chip IDs.

Or, if the list in PupScan does not identify Cardbus/PCMCIA, can you deduce which one by elimination?
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: Possible fix for the missing yenta-socket problem

#33 Post by BarryK »

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:

Code: Select all

yenta-socket 0x00001217 0x00006933 #O2 Micro, Inc. CardBus/SmartCardBus Controller v4.00
Please report whether this works, so we can advocate its inclusion in the final. Thanks.
Richard
Ah, you're one step ahead of me. Rerwin and mbe, you must have already been through this exercise somewhere else in the forum.

mbe, put that special case in and let us know if it works -- do this quickly and it will go into the 4.00final.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: Good workaround

#34 Post by BarryK »

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
Ahem, I should read ahead before posting!
Ok, I'll put it in.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: BCM43xx, Personal Storage file problems

#35 Post by BarryK »

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.
With the .25 kernel, the bcm43xx module is replaced by b43 and b43legacy modules.

Ah, yes, comboformat has a bug, I haven't had time to fix it. It saves a session to the second partition, but then dosn't recognize it at bootup. I have put a notice into the Universal Installer not to use ComboFormat for now, until the bug is fixed.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#36 Post by BarryK »

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. :evil:

?!? - Previous Puppies, including Dingo Alphas &Betas, had no problems at that -- MD5sum checked OK. Will try on other machines, with an external card reader.
I'm also running Dingo with k2.6.21.7. I plugged in an SD card, ran Pmount, there it is, mounts ok.

So, no problem. Is your SD card recognized in Pup 3.01?
[url]https://bkhome.org/news/[/url]

JustGreg
Posts: 782
Joined: Tue 24 May 2005, 10:55
Location: Connecticut USA

#37 Post by JustGreg »

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.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#38 Post by BarryK »

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.
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?

I was just going to comment "I hope that the message about not supporting WPA hasn't been hardcoded into the script for certain modules", when I decided to take a look at the wag-profiles.sh script. It has this:

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
Curses, it has been.
I really don't want to have to patch that bit of code for the changing situation with wireless modules. They are in a state of constant development, and now we have a bunch of new ones with the 2.6.25 kernel.

Can anyone think of a better way to do the above? or, do we just have to update it regularly?
[url]https://bkhome.org/news/[/url]

NathanO
Posts: 210
Joined: Fri 23 Feb 2007, 00:03
Location: San Antonio, TX

#39 Post by NathanO »

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?

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#40 Post by BarryK »

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?
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.

Ok, it has booted up, but no mouse. Do CTRL-ALT-BACKSPACE, or whatever to get a commandline, run:

# lsmod

...has 'usbhid' module loaded?

File /etc/rc.d/rc.local0 has this line in it, for detecting a USB mouse:

[ ! "`cat /proc/bus/usb/devices 2>/dev/null | grep -i "Cls=03(HID ) Sub=01 Prot=02"`" = "" ] && USBMOUSEDEV="input/mice"

It may be that this line is different in your case. Try:

# grep -i "Cls=03(HID ) Sub=01 Prot=02" /proc/bus/usb/devices

If that line ain't there, can you find what it has changed to?
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#41 Post by BarryK »

From the commandline you can use the mp text editor:

# mp /proc/bus/usb/devices

to poke around in that file.
[url]https://bkhome.org/news/[/url]

big_bass
Posts: 1740
Joined: Mon 13 Aug 2007, 12:21

#42 Post by big_bass »

BarryK wrote:
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.
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?

I was just going to comment "I hope that the message about not supporting WPA hasn't been hardcoded into the script for certain modules", when I decided to take a look at the wag-profiles.sh script. It has this:

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
Curses, it has been.
I really don't want to have to patch that bit of code for the changing situation with wireless modules. They are in a state of constant development, and now we have a bunch of new ones with the 2.6.25 kernel.

Can anyone think of a better way to do the above? or, do we just have to update it regularly?
Barry K
strangely I had a problem with wifi with my xvesa fatfree 3.01
IRC user neur1 told me version 3.00 worked for him and version 3.01 wifi no

so for him I modified the version 3.00 wag profiles script and added a driver to it just in case and added xorg back burned another CD and all was fine but without the edited script ? I used the standard 3.01 script un edited and it worked this time I never found out why :? since it worked I just forgot about this until I saw this report

but just for the record there was a change here in the wag profiles script from version 3.00 to version 3.01
I hope this can help you somehow

the re burn of the CD fixed my problem with that I hope you have the same good luck
with this

this below image is what changed from version 3.00 to version 3.01 note I hand edited the script and only added the zd1211rw to the 3.00 script I noticed there was a change for the USB too

PS Your puppy 4 looks great I love the new look and many of the new apps you added :wink:


big_bass
Attachments
3.00 script I added the zd1211rw to it .png
(18.08 KiB) Downloaded 1381 times
Last edited by big_bass on Sun 04 May 2008, 03:06, edited 3 times in total.

User avatar
Lobster
Official Crustacean
Posts: 15522
Joined: Wed 04 May 2005, 06:06
Location: Paradox Realm
Contact:

#43 Post by Lobster »

BarryK wrote: 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.
I had the same bootup lock of the mouse with Ubuntu hardy heron which as far as I can tell uses kernel 2.6.24

Will try the suggested probe when next booting with the 2.5 kernel in a while :)
Puppy Raspup 8.2Final 8)
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html :D

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#44 Post by kirk »

Pupdial has been broke for me since beta1. My init2 string is Init2 = AT$QCMDR=3, but shows up as AT3. I guess the $ is messing it up in beta2 - sc1. If i change line 177 from:

<input>echo \"${INIT2M}\"</input>


to


<default>\"${INIT2M}\"</default>


like it was in beta1, then it works correctly as it did in the past. I guess line 170, which is init1, would have the same problem.

P.S.:

Going to post the kernel source for 2.6.25 or a sfs file of it?

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#45 Post by John Doe »

here is my report:

I tested both versions on 4 different machines with all types of configurations.

found a couple small problems. some have already been reported, but I'll keep them in there just for informational purposes.

1-in version 2.6.25 USB keyboards and mice do not seem to work when plugged into USB1.1. I'm using a mouse right now with USB 2.0 and it works ok. Perhaps a missing module in initrd?

2-in version 2.6.25 kernel, I have trouble with sound on one machine. It works with 2.6.21.7. I compared the modules loaded by each version on the machine in question and found that 2.6.21.7 loads three more than 2.6.25 does.

snd
soundcore
snd_hwdep

the first two appear to be missing ("Fatal: Module * not found", when I modprobe) and the third loads but doesn't fix the problem.

On the other three machines, sound works fine with either version.

3-bcw43xx driver is missing. The firmware looks like it's there, but it isn't in the list of modules under the networking wizard. *note, I read what you wrote about b43, but that says it's for a PCMCIA BUS and mine is on the board in a laptop. I don't see b43legacy in the list.

4-Hotpup (under 2.6.21.7) only lists the first optic drive (dvd/cd) when two are present. Same behavior whether they are sr0,sr1 or hda0,hda1 (SCSI/IDE ). Both drives are listed ok in 2.6.25 on both machines in question.

5-Had some seamonkey crashes when running Flash Player. Tried to diagnose by launching seamonkey from the shell but haven't gotten it to crash again. The only info I've gotten is this warning:

Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8

I'll keep trying to get an error, but for the time being I'm just chalking this one up as the flash player is a POS. Hopefully they fix it in the next version.

6-can't copy and paste between rxvt and geany.

other than those few things, all is perfect. Looks like the best release yet.

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

Log formatting in rc.modules

#46 Post by rerwin »

Barry,
I was going to wait for later, but since you requested easy-to-fix issues...

In improving the formatting of bootsysinit.log, the "loading" messages did not get indented as I recommended. Please insert two spaces before the text in lines 124 and 174 of /etc/rc.d/rc.modules, as:

Code: Select all

    echo "  loading module $MODULE"
Thanks.
Richard

User avatar
prit1
Posts: 542
Joined: Fri 04 Jan 2008, 00:10
Location: Los Angeles

#47 Post by prit1 »

@Barryk: My Averatec 3225 HS laptop with RT2500 wireless module works perfectly well in Puppy version 2.17.1. But in the Dingo 4.00. I have to run the Network Wizard everytime I login and only then the wireless network would start working. This is inspite of the profile being saved. This happens for both kernels.

geneven
Posts: 87
Joined: Thu 04 Oct 2007, 19:36
Location: Agoura Hills, California

BCM43xx

#48 Post by geneven »

"With the .25 kernel, the bcm43xx module is replaced by b43 and b43legacy modules. "

Well, they don't work for me. I guess I'll have to stay with the older kernel.

User avatar
Lobster
Official Crustacean
Posts: 15522
Joined: Wed 04 May 2005, 06:06
Location: Paradox Realm
Contact:

#49 Post by Lobster »

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.
:cry: Suddenly realised - I am using a ps2 mouse and keyboard (both lock) During the bootup at the choose locale, I can not scroll down - no keyboard response. Once I got to the desktop but the mouse was not working . . .
Puppy Raspup 8.2Final 8)
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html :D

jonyo

#50 Post by jonyo »

Just a quick report. Compaq sr2020nx (AMD Athlon 64 3500+ / 2.2 GHz, NVIDIA GeForce 6150 LE) 2 gig ram, d-link dwl-g122 ver b1 usb wifi dongle using the win Netrtusb .inf (rt2500) with wep 64 hex. Thing's worked on everything I've tried right down through to 2.12.

Didn't see the native rt2570 available so dloaded the enhanced 1.6.1 ..but haven't sorted that out yet.

Have to use xvesa cos I lose the mouse cursor with xorg (prob goes back to 2.15 for me on this box), Apparently someone else does also with the same onboard graphics. Haven't tried the Nvidia driver yet though.. Thought I had a fix suggested by prehistoric the other day but the prob came back, but is much better.

At first glance, quite a few changes here from 3xx soo..have some catching up to doo..

dingo k2.6.25 setup with linNwin & xpsp2
Last edited by jonyo on Sun 04 May 2008, 07:28, edited 1 time in total.

Post Reply