Puppy 4.1.1 release candidate
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Puppy 4.1.1 release candidate
This is announced on my blog:
http://puppylinux.com/blog/?viewDetailed=00452
This thread is for reporting bugs. I would like to aim at getting the final out about a week from now.
I have already discovered a couple of bugs:
1.
I removed the Pppoeconf package, but it is still in the selection buttons in the Internet Connection Wizard.
2.
My audio tray applet has disappeared. The only alsa change from 4.1 I think is at shutdown in /etc/rc.d/rc.shutdown -- I m using the rc.alsa script to "stop" alsa.
http://puppylinux.com/blog/?viewDetailed=00452
This thread is for reporting bugs. I would like to aim at getting the final out about a week from now.
I have already discovered a couple of bugs:
1.
I removed the Pppoeconf package, but it is still in the selection buttons in the Internet Connection Wizard.
2.
My audio tray applet has disappeared. The only alsa change from 4.1 I think is at shutdown in /etc/rc.d/rc.shutdown -- I m using the rc.alsa script to "stop" alsa.
[url]https://bkhome.org/news/[/url]
Hi Guys,
Here's another (high speed) server for 4.1.1rc to share the load.
http://puppylinux.igsobe.com/puppylinux ... iles/test/
Best,
Eric
Here's another (high speed) server for 4.1.1rc to share the load.
http://puppylinux.igsobe.com/puppylinux ... iles/test/
Best,
Eric
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
Bugs
As per previous 4.x series, the bcm43xx is not detected, but an other card is. Yes there have been posted work a rounds, but how about the new user to Puppy?
Is there anything we can do about this so detection is correct for everyone?
Is there anything we can do about this so detection is correct for everyone?
Re: Bugs
I just updated 4.0 to 4.1 retro. In the files put aside to /tmp there were a couple of things that may be of interest. One was commented "Is a kernel issue, report to ..." and the other obviously was related to Broadcom and bcm43xx that my PC has. I can send PM "to whom it may concern", or add the files to the forum.NathanO wrote:As per previous 4.x series, the bcm43xx is not detected, but an other card is. Yes there have been posted work a rounds, but how about the new user to Puppy?
Is there anything we can do about this so detection is correct for everyone?
Rgds, zgp152
4.1.1rc won't boot on Dell Precision M70 laptop
Please ignore, bad burn/download.
- SaltLattice
- Posts: 1
- Joined: Fri 24 Oct 2008, 22:40
- Location: Germany
chmsee Bug
Hi, Puppy 4.1.1rc is running perfect on my Toshiba SatellitePro 4600 Notebook with WLAN Intel 2200b/g Chip. Thank you. I contribute only this little Puppy Bugreport:
chmsee does not load chmfiles, if clicked within ROX-Filer.
Must edit first "Set RUN Action" the "shell Command" from chmseeshell "$1" to chmsee "$1". Then it works.
But chmsee still crashes while loading winfaq.chm
http://www.winfaq.de/download_winfaq.htm
Error message in rxvt: "Segmentation fault".
kchmviewer works fine with winfaq.chm, maybe a bug with chmsee - not Puppy.
chmsee does not load chmfiles, if clicked within ROX-Filer.
Must edit first "Set RUN Action" the "shell Command" from chmseeshell "$1" to chmsee "$1". Then it works.
But chmsee still crashes while loading winfaq.chm
http://www.winfaq.de/download_winfaq.htm
Error message in rxvt: "Segmentation fault".
kchmviewer works fine with winfaq.chm, maybe a bug with chmsee - not Puppy.
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
4.1.1rc on Dell D600
Now running 4.1.1rc k2.6.25.16 off CD on my Dell Latitude D600 (1.4 GHz , 1.25 GB, no hard drive). Only problem so far is with network wizard setting up the ra2500 mini-pci card. Everything works until the wizard says it has made the connection, but blinky does not appear in the tray. Running Pwireless, after wireless firmware has loaded, does launch blinky when I connect through Pwireless.
Everything else looks good on this machine. More tests to follow.
Everything else looks good on this machine. More tests to follow.
4.1.1 experience
Good news:
- Synaptic touch pad on Dell 8200 correctly detected and configured
Not good news:
- Network Wizard still fails re wireless. Must continue using my configuration script for broadcom and atheros pcmcia cards.
General assessment:
- 4.1.1 is excellent overall
...to be continued.
- Synaptic touch pad on Dell 8200 correctly detected and configured
Not good news:
- Network Wizard still fails re wireless. Must continue using my configuration script for broadcom and atheros pcmcia cards.
General assessment:
- 4.1.1 is excellent overall
...to be continued.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: 4.1.1 experience
If 4.00 worked for you, the old 4.00-based Network Wizard is available if 4.1.1rc, look in the "Setup" menu, entry "Network Wizard (old version)".dogone wrote:- Network Wizard still fails re wireless. Must continue using my configuration script for broadcom and atheros pcmcia cards.
The files have got relocated so as not to clash with the new Wizard, and I have only done basic testing of that.
The purpose of the old Wizard is just to see if you can get networking going, then we can find out what is different and fix the new Wizard. So I see the old Wizard as only temporarily in Puppy, probably it won't be in 4.2.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Bugs
If you have a fix, then you need to post it here.zgp152 wrote:I just updated 4.0 to 4.1 retro. In the files put aside to /tmp there were a couple of things that may be of interest. One was commented "Is a kernel issue, report to ..." and the other obviously was related to Broadcom and bcm43xx that my PC has. I can send PM "to whom it may concern", or add the files to the forum.NathanO wrote:As per previous 4.x series, the bcm43xx is not detected, but an other card is. Yes there have been posted work a rounds, but how about the new user to Puppy?
Is there anything we can do about this so detection is correct for everyone?
Rgds, zgp152
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Puppy 4.1.1 release candidate
This is now fixed, see my blog post:BarryK wrote:2.
My audio tray applet has disappeared. The only alsa change from 4.1 I think is at shutdown in /etc/rc.d/rc.shutdown -- I m using the rc.alsa script to "stop" alsa.
http://puppylinux.com/blog/?viewDetailed=00453
You can easily edit /etc/rc.d/rc.services and apply this fix to 4.1 and 4.1.1rc.
[url]https://bkhome.org/news/[/url]
Re: Bugs
I solved the Broadcom problem by adding a script (iwconfig etc.) to rc.local. So for the wizard + Broadcom combination, I have no fix. The texts that I refer to did not help me in any way; perhaps coders may get something out of them.BarryK wrote:If you have a fix, then you need to post it here.zgp152 wrote:I just updated 4.0 to 4.1 retro. In the files put aside to /tmp there were a couple of things that may be of interest. One was commented "Is a kernel issue, report to ..." and the other obviously was related to Broadcom and bcm43xx that my PC has. I can send PM "to whom it may concern", or add the files to the forum.NathanO wrote:As per previous 4.x series, the bcm43xx is not detected, but an other card is. Yes there have been posted work a rounds, but how about the new user to Puppy?
Is there anything we can do about this so detection is correct for everyone?
Rgds, zgp152
Rgds zgp152
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Good news for Medion 8818 owners
For reasons a little long to explain, I felt compelled to burn a CD of 4.1.1
(with Lin'N'Win I normally don't burn a CD anymore)
I tried the normal version on my Medion MD8818
I to my big (and pleasant) surprise, my first sata HDD, connected to a VIA controller 5287 which is set in IDE mode, is recognized now.
To my deception however the second sata, connected to an external e-sata bay isn't recognized.
Any way good news for fellow posters having a MD8818.
(with Lin'N'Win I normally don't burn a CD anymore)
I tried the normal version on my Medion MD8818
I to my big (and pleasant) surprise, my first sata HDD, connected to a VIA controller 5287 which is set in IDE mode, is recognized now.
To my deception however the second sata, connected to an external e-sata bay isn't recognized.
Any way good news for fellow posters having a MD8818.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Hi everyone,
Concerning bcm43xxx...
Puppy 4.1 is the first official release to have wifi working out of the box on my laptop (with chipset bcm43xxx) since 2.16.1 !
So when I read Nathan0's comment, I couldn't help downloading the 4.1.1rc to check the behaviour.
Ouf ! It's still working !
Hope future fixes won't break it...
Concerning bcm43xxx...
Puppy 4.1 is the first official release to have wifi working out of the box on my laptop (with chipset bcm43xxx) since 2.16.1 !
So when I read Nathan0's comment, I couldn't help downloading the 4.1.1rc to check the behaviour.
Ouf ! It's still working !
Hope future fixes won't break it...
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
More good news.
In the past I had problems to get the USB wan working with RT73.
No it works out of the box.
No it works out of the box.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Second HDD sata not recognized
I have an external HDD with a drive which is the same as the internal (now recognized) one in the MD8818.
This HDD is in the e-sata bay, which is connected to the same VIA controller 5287 as to which the internal HDD is connected.
Sadly this HDD isn't recognized and unfortunately all my important data is on this external HDD.
probepart gives
sda1 being the internal sata HDD (c:\)
sda5 being an extended partition (d:\)
sdb1 is a 8GB flash drive. plugged in
sdc1 is a 1GB flash card plugged in
sdd and sde are slots from the multi reader for memory sticks, etc.
fdisk -l gives
What else can I do for detecting this external sata HDD?
This HDD is in the e-sata bay, which is connected to the same VIA controller 5287 as to which the internal HDD is connected.
Sadly this HDD isn't recognized and unfortunately all my important data is on this external HDD.
probepart gives
Code: Select all
# probepart
/dev/sda1|ntfs|584171532
/dev/sda2|none|2
/dev/sda5|vfat|40965686
/dev/sdb1|ext2|16113132
/dev/sdc1|vfat|2001824
/dev/sdd|none|0
/dev/sde|none|0
/dev/sr0|none|2097150
/dev/sr1|none|2097150
#
sda5 being an extended partition (d:\)
sdb1 is a 8GB flash drive. plugged in
sdc1 is a 1GB flash card plugged in
sdd and sde are slots from the multi reader for memory sticks, etc.
fdisk -l gives
Code: Select all
# fdisk -l
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 36363 292085766 7 HPFS/NTFS
/dev/sda2 36364 38913 20482875 f W95 Ext'd (LBA)
/dev/sda5 36364 38913 20482843+ b W95 FAT32
Disk /dev/sdb: 8254 MB, 8254390272 bytes
255 heads, 63 sectors/track, 1003 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 1003 8056566 83 Linux
Disk /dev/sdc: 1024 MB, 1024966656 bytes
32 heads, 63 sectors/track, 993 cylinders
Units = cylinders of 2016 * 512 = 1032192 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 993 1000912+ 6 FAT16
#
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
I've fixed the problems with the gtk2jwm themes. No changes where necessary to the gtk2jwm script itself.
1) I have tweaked the gradient-grey and gradient-brown themes so that they include declarations for all the colours needed to build a jwm theme with sufficient contrast. I also bumped the font size for brown down from 12 to 10 to give greater differentiation between the themes.
2) I have edited /etc/xdg/templates/_root_.jwmrc so that it has a more neutral theme as default (mainly based on the jwm original theme). This means that when gtk2jwm cannot find enough information the the gtkrc it doesn't default back to the garish (in some peoples opinion) citrus-cut jwm theme.
3) I also moved the keybindings general config options and Startup tags from _root_.jwmrc to jwmrc-personal they were mainly duplicated here anyway. I think it was confusing to have them declared twice and it has certainly confused me in the past when I've edited the wrong one and it has had no effect. On that note I am unsure what application uses jwmrc-personal2 which also contains duplicate declarations.jwmrc-personal. It might be possible to remove this though maybe not in a full release without some testing.
4) Gtk themes original,raleigh and emacs inherit most or all of their config from the gtk default so gtk2jwm does not work for them, but the jwm default is now closer to their style. Emacs only contains key bindings so it might be clearer to rename the emacs theme to "Raleigh(Emacs_keybindings)".
1) I have tweaked the gradient-grey and gradient-brown themes so that they include declarations for all the colours needed to build a jwm theme with sufficient contrast. I also bumped the font size for brown down from 12 to 10 to give greater differentiation between the themes.
2) I have edited /etc/xdg/templates/_root_.jwmrc so that it has a more neutral theme as default (mainly based on the jwm original theme). This means that when gtk2jwm cannot find enough information the the gtkrc it doesn't default back to the garish (in some peoples opinion) citrus-cut jwm theme.
3) I also moved the keybindings general config options and Startup tags from _root_.jwmrc to jwmrc-personal they were mainly duplicated here anyway. I think it was confusing to have them declared twice and it has certainly confused me in the past when I've edited the wrong one and it has had no effect. On that note I am unsure what application uses jwmrc-personal2 which also contains duplicate declarations.jwmrc-personal. It might be possible to remove this though maybe not in a full release without some testing.
4) Gtk themes original,raleigh and emacs inherit most or all of their config from the gtk default so gtk2jwm does not work for them, but the jwm default is now closer to their style. Emacs only contains key bindings so it might be clearer to rename the emacs theme to "Raleigh(Emacs_keybindings)".
- Attachments
-
- gtk2jwm-fix.tar.gz
- (3.24 KiB) Downloaded 534 times
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
Oops! Mouse-change fixes not yot complete
When a mouse type is changed using the mouse wizard, the corresponding protocol is no longer set in xorg.conf. In moving the protocol logic from input-wizard to xwin, I did not verify the validity of the surrounding if-tests. Now the "oldmousedevice does not get updated to indicate other than "first time", so the protocol code does not execute for a wizard-change (unless the mouse has previously been changed and re-detected by a reboot, which was probably the case when I originally tested it)..
The fix is to re-order the first two tests and move the oldmousedevice update out one level, so that the first test is for different old and new types, then the test for first time (oldmousedevice = "nothing"). Oldmousedevice should get updated any time the type values differ. Affected xwin code beginning at line 155:The updated xwin and its difference file are attached.
Richard
The fix is to re-order the first two tests and move the oldmousedevice update out one level, so that the first test is for different old and new types, then the test for first time (oldmousedevice = "nothing"). Oldmousedevice should get updated any time the type values differ. Affected xwin code beginning at line 155:
Code: Select all
#v411 restored after removal in v407...
#update xorg.conf if mouse has changed...
MOUSEDEV="`cat /etc/mousedevice`" #autodetected in rc.sysinit
OLDMOUSEDEV="`cat /etc/oldmousedevice`" #set in rc.sysinit
if [ ! "$OLDMOUSEDEV" = "$MOUSEDEV" ];then
if [ ! "$OLDMOUSEDEV" = "nothing" ];then #"nothing" on first boot.
if [ -f /etc/X11/xorg.conf ];then
. . .
fi
fi
OLDMOUSEDEV="$MOUSEDEV" #v411 old is now current mouse
echo -n "$OLDMOUSEDEV" > /etc/oldmousedevice #v411
fi
Richard
- Attachments
-
- new_mouse_fix.tar.gz
- Xwin correction to support mouse change via wizard.
- (7.25 KiB) Downloaded 478 times
not so much a bug but unexpected behaviour
I did a manual frugal install and booted it with pfix=ram.
When X started it showed the boot partition as mounted with a yellow circle not unmountable. Mount confirmed the partition as mounted, I could unmount it from a terminal and the icon upated accordingly. I think I have seen this reported before, maybe in relation to 4.1.
I did a manual frugal install and booted it with pfix=ram.
When X started it showed the boot partition as mounted with a yellow circle not unmountable. Mount confirmed the partition as mounted, I could unmount it from a terminal and the icon upated accordingly. I think I have seen this reported before, maybe in relation to 4.1.
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]