The Official Release of Lucid 5.25 (Lucid Five Twenty-Five)
modem-modprobe pkg pinstall & pusbmodeswitch_protect fixed
01micko,
Just so everyone knows, I have re-uploaded the modem-modprobe package with those scripts corrected, after the eighth download of it. Anyone needing to apply the package to a "build" or "sandbox" environment should use this later version. If it still fails or is insufficient for what you are doing, please report that here and I will deal with it. Thanks for your patience.
Richard.
Just so everyone knows, I have re-uploaded the modem-modprobe package with those scripts corrected, after the eighth download of it. Anyone needing to apply the package to a "build" or "sandbox" environment should use this later version. If it still fails or is insufficient for what you are doing, please report that here and I will deal with it. Thanks for your patience.
Richard.
Some ideas for the pupsave update process
Considerations for pupsave update regarding the modem-modprobe upgrade:
1. The file /etc/modprobe.d/blacklist-modem.conf, which allows the user to blacklist sound-card modem snd-atiixp-modem, snd-intel8x0m, snd-via82xx-modem by uncommenting the appropriate lines, will now get deleted at bootup.
a. This blacklisting should not now be necessary since the user can erase that detection in pupdial and then probe for a USB modem that may not have been ready at bootup.
b. If this conf file needs to be retained, it should be renamed in Luci to anything not beginning with "blacklist" or "modem_"; recommend "snd-modem_blacklist.conf".
c. Since the users' modified file will not exist after an update, users need to be aware of that and will need to re-edit their change into /etc/modprobe.d/snd-modem_blacklist.conf (assuming the above example is used)
2. Some obsolete files and directories should be removed during an update to 255 or later, in case the user might have modified them:If you need me to put all this into a script for invocation by rc.update, just ask. Please also tell me if some of these deletions are unnecessary because they are already eliminated by rc.update.
These may not solve any of the reported problems, but would clean up any user mods of these obsolete files.
Richard
1. The file /etc/modprobe.d/blacklist-modem.conf, which allows the user to blacklist sound-card modem snd-atiixp-modem, snd-intel8x0m, snd-via82xx-modem by uncommenting the appropriate lines, will now get deleted at bootup.
a. This blacklisting should not now be necessary since the user can erase that detection in pupdial and then probe for a USB modem that may not have been ready at bootup.
b. If this conf file needs to be retained, it should be renamed in Luci to anything not beginning with "blacklist" or "modem_"; recommend "snd-modem_blacklist.conf".
c. Since the users' modified file will not exist after an update, users need to be aware of that and will need to re-edit their change into /etc/modprobe.d/snd-modem_blacklist.conf (assuming the above example is used)
2. Some obsolete files and directories should be removed during an update to 255 or later, in case the user might have modified them:
Code: Select all
rm -f /etc/modprobe.conf #replaced by puppy.conf and alsa.conf:
rm -rf /etc/modprobe_includes 2>/dev/null #obsolete
rm -rf /etc/usb_modeswitch.d
rm -f /etc/usb_modeswitch.d-*
rm -f /etc/modemttyUSBnum
rm -f /usr/sbin/pusbmodeswitch_adapt
rm -f /etc/udev/rules.d/40-usb_modeswitch-adapted.rules
rm -f /etc/udev/rules.d/41-usb_modeswitch-puppy.rules
rm -f /etc/udev/rules.d/50-usb_modeswitch-option.rules
rm -f /etc/udev/rules.d/50-usb_modeswitch-usbserial.rules
#Force update of modem initialization scripts...
rm -f /etc/modules/firmware.inst.2.* #renamed to firmware.dep.inst.$KERNVER
rm -f /etc/modules/firmware.dep.inst.2.*
#Remove any installed obsolete initialization scripts...
rm -f /etc/init.d/Ipw
rm -f /etc/init.d/Motomodem
rm -f /etc/init.d/Option
rm -f /etc/init.d/Pl2303
rm -f /etc/init.d/Qcserial
rm -f /etc/init.d/Sierra
rm -f /etc/init.d/Ti_usb_3410_5052
rm -f /etc/init.d/alsa
#Remove current modem selection, to force re-detection...
rm -f /dev/modem
These may not solve any of the reported problems, but would clean up any user mods of these obsolete files.
Richard
I know nothing but my experience do support that we should warn people to never do such upgrading without first booting with pfix=ram and then making a copy of the pupsavefile they want to upgrade and maybe even rename the copy to something puppy don't recognize and then reboot without save and boot into the new version and try to upgrade for several days before accepting that the upgrade went smoothly.
Barry have written on his blog that he does not recommend such upgrading. The scripts are not good enough to handle some dependencies.
It is a hit and miss thing.
Barry have written on his blog that he does not recommend such upgrading. The scripts are not good enough to handle some dependencies.
It is a hit and miss thing.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Thanks bigpup and Nooby for your answers and consideration.
It goes without saying that I always do a full system backup before upgrading. So nothing was lost.
The one thing I can try is to do a fresh upgrade for each and every nvidia driver. That I did not do earlier today. And it is very much possible, that the first driver (260) was wrong and the following installations (256, 195 etc) just messed up xorgwizard. Will try and report back this weekend.
Just for information: Quickpet recommended nvidia 260.19.12 which turned out to be definitely the wrong choice. So what is this recommendation based on?
It goes without saying that I always do a full system backup before upgrading. So nothing was lost.
The one thing I can try is to do a fresh upgrade for each and every nvidia driver. That I did not do earlier today. And it is very much possible, that the first driver (260) was wrong and the following installations (256, 195 etc) just messed up xorgwizard. Will try and report back this weekend.
Just for information: Quickpet recommended nvidia 260.19.12 which turned out to be definitely the wrong choice. So what is this recommendation based on?
http://distro.ibiblio.org/pub/linux/dis ... ucid52.pet
TOR-Browser Complete 1.1.5
Oh get this, if your cpu clock is not correct then TOR Browser stops halfway in its startup routine and doesn't tell you why. How long do you think it took me to learn that? The cure is to run Psync before TOR.
TOR-Browser Complete 1.1.5
Oh get this, if your cpu clock is not correct then TOR Browser stops halfway in its startup routine and doesn't tell you why. How long do you think it took me to learn that? The cure is to run Psync before TOR.
i had a similar problem to wuwei , x wouldn't start at all. But it did after a reboot. I ended up starting afresh anyway as i found that guvcview didn't work as i didn't uninstall the pet of it before upgrading. All is working fine though now..
I'm pleased to say though that i've had no sound problems so far (losing sound after reboot). This problem used to occur multiple times a day, especially if i booted into another puppy, then came back to lupu or luci. I'm keeping my fingers crossed, and hoping that this rather large luci/lupu bug is finally fixed.
Thankyou rerwin and playdays
I'm pleased to say though that i've had no sound problems so far (losing sound after reboot). This problem used to occur multiple times a day, especially if i booted into another puppy, then came back to lupu or luci. I'm keeping my fingers crossed, and hoping that this rather large luci/lupu bug is finally fixed.
Thankyou rerwin and playdays
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
It is based on the vendorID/productID of the chipset.wuwei wrote:Just for information: Quickpet recommended nvidia 260.19.12 which turned out to be definitely the wrong choice. So what is this recommendation based on?
This is found out by running:
Code: Select all
lspci -nn|grep VGA
This is compared to a database that is in Quickpet. The path is /usr/local/grphics-text where you will find 3 nvidia files and an ATI file. The database was taken from the official nVidia site, ftp://download.nvidia.com/XFree86/Linux ... chips.html
HTH, and if you find something wrong let me know.
I may have actually taken the database from the 256 version, it may be different, just check your card with the data on the official nvidia site, what driver does work for you?
Puppy Linux Blog - contact me for access
I have made a bad mistake. I believe we have set a decent example of not adding new code right before release. And because of that Lucid had a decent record for stability. Unfortunately I blew it on the new material by rerwin. It is too much new code to put in right before release and I should have realized that. It makes broad system level changes and there is no way I should have tried to implement it. No matter how good the programmer, new code before release *will* cause problems. Everyone knows that, I just blew it.
So I apologize to rerwin and I apologize to our testers.
Luci-256 is available in the first message of this thread.
In testing, upgrades from the previous luci version are not the most important thing now--most testing should be done pfix=ram. And then at the end we will test upgrading Lucid 5.2.
So I apologize to rerwin and I apologize to our testers.
Luci-256 is available in the first message of this thread.
In testing, upgrades from the previous luci version are not the most important thing now--most testing should be done pfix=ram. And then at the end we will test upgrading Lucid 5.2.
Fresh manual frugal install on the old P4 test box. Display,sound and internet all working on initial boot.
Installed Xorg-High and SeaMonkey 2.0.11 so far.
VIDEO REPORT: Lucid Puppy, version 256
Chip description:
Intel Corporation 82865G Integrated Graphics Controller
Driver used by Xorg:
Video mode used by Xorg:
Resolution: Depth:
...the above also recorded in /tmp/report-video
#
# glxgears
2528 frames in 5.0 seconds
3121 frames in 5.0 seconds
2733 frames in 5.0 seconds
2832 frames in 5.0 seconds
2829 frames in 5.0 seconds
Ethernet controller : Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02)
Multimedia audio controller : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
VGA compatible controller : Intel Corporation 82865G Integrated Graphics Controller (rev 02)
Looking good here so far.
Installed Xorg-High and SeaMonkey 2.0.11 so far.
VIDEO REPORT: Lucid Puppy, version 256
Chip description:
Intel Corporation 82865G Integrated Graphics Controller
Driver used by Xorg:
Video mode used by Xorg:
Resolution: Depth:
...the above also recorded in /tmp/report-video
#
# glxgears
2528 frames in 5.0 seconds
3121 frames in 5.0 seconds
2733 frames in 5.0 seconds
2832 frames in 5.0 seconds
2829 frames in 5.0 seconds
Ethernet controller : Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02)
Multimedia audio controller : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
VGA compatible controller : Intel Corporation 82865G Integrated Graphics Controller (rev 02)
Looking good here so far.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
more testing - sounds like a plan . . .I have made a bad mistake
I was using Openbox (not JWM - which incidentally was working very well in Luci255 and 254)
with 255 and the sound was working
but somehow I had the icon turned to muted (red icon appeared)
- but it was not muted - could not rectify this. Will see if it happens in 256
Starting from a 'puppy pfix=ram' of Luci-256
Sound is persistent
but I still have to 'connect again' after the first reboot with the simple sns connection option for my Ethernet - it is then persistent
during first saving
my max puppy file size to save to is 1.2 (a larger option was available as a pet
- not yet available?)
I used FireFox 3.6.13 and immediately updated to 3.6.15
It advised me to update Adobe - so I did
Will see how this works out with my Youtube streaming crashes . . .
Was using the 4 beta Firefox previously - even though in many ways I probably prefer Seamonkey . . .
Working with pristine Puppy's I have to keep logging into the forum and other password protected sites so recommend this (if you are a non-paranoid only)
https://lastpass.com/misc_download.php
I used and installed Micks excellent LibreOffice experimental locales SFS creator
- how cool is that? (clue: very)
http://www.murga-linux.com/puppy/viewto ... 027#505027
Larry apologisng always a good idea (OK I am English)
even when not required
Thanks guys. OK more tweaking . . . but first a cup of tea . . .
Puppy Linux
Your Humble Penguin
i spoke too soon about luci255, booted this morning and no sound ....... i'm starting to hate the alsa sound wizard . why can puppy always automatically find my card when booting pfix=ram, yet randomly fail to after creating a savefile?
my card is C-media CM8728(rev10)
there is also an audio output on my video card that i don't use and also an on board sound card that is disabled in the bios (it's broken) and there for doesn't show in alsa wizard.
actually, whilst writing this, i've just run the alsa wizard and it got this error
slave
aplay: main:608: audio open error: No such device
was working fine when turned off last night
.......on to 266
my card is C-media CM8728(rev10)
there is also an audio output on my video card that i don't use and also an on board sound card that is disabled in the bios (it's broken) and there for doesn't show in alsa wizard.
actually, whilst writing this, i've just run the alsa wizard and it got this error
slave
aplay: main:608: audio open error: No such device
was working fine when turned off last night
.......on to 266
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Pmusic upgraded to version 1.6.6
http://www.murga-linux.com/puppy/viewtopic.php?t=31206
http://www.murga-linux.com/puppy/viewtopic.php?t=31206