Ppup-417 Alpha bug reports
___090720-25 pP417std testing___
.. following Flash's lead (somewhat)
1) Burniso2cd of pup4-417-k2.6.30.1.iso to RIDATA 1-4x CD-RW media on DVD-RW IDE1004 unit in P412bone1 (an initial for Xorg, a repeat for Xvesa - both burns 'pinkslipped' by Verify despite proper 4x burn, OK/casebutton-closetray procedure for 1st .. OK did a s/w close of tray on 2nd, just thought I'd try any variation in sequence/procedure to try for a greencard from Verify but sometimes it simply doesn't ). Both actually good.
2) boot 'Xorg' disc with pfix=ram for a peek ... Xorg is still a *mess* to get past for me on my usual machine (I think I guessed lucky .. Mileage May Vary). Leafpad seems a better choice for simple opener of text or at least in openwith (should I edit readmes?). Perhaps make bookmarks to local html like Roxhelps for Pupbrowser (all the wikientries in the world aren't going to help a conn that ain't) - of course one can always play with the url to navigate. Is freetype in? the fonts might be better (quibblequibble). Actually it's quite good for a final(?) alpha as far as a quick look goes in my limited testing. poweroff/nosave.
3) Xvesa (simpler, quicker re-X)
a) started uP476std,Xvesa - this is a fairly mature liveCD tester set up for my comfort and almost entirely stable. gdm-reported disc-size is approx. 237Mb total with 10 savedirs .. switch disc to the 'Xvesa' pP417 and save current session to this disc on poweroff. long-ish 1st "Burning data from previous CD to first track...", then after red "The media tray appears to be open"etc mssg a shorter 2nd burn & autoeject
b) coldboot, both upgrade savedirs then 417's sfs loaded - upgrade successful
4) Xorg
a&b) pretty much the same shutdown, save to switched disc upgrade procedure but used P421barebones,Xorg as the starting liveCD (gdm-reported disc-size approx. 136Mb total with 7 savedirs)
...5) general impressions of both upgrades
Some minor issues even though both successful. A re-install of leafpad may work best if one prefers it to NicoEdit for a simple textviewer/editor (zedit doesn't get 'broken'). SeaMonkey upgrades to 1116 but Medit stayed at earlier 92 version (seems to be fixed with a simple switch of /usr/bin/medit from a renamed click-mounted copy of the liveCD's pup4-417.sfs on thumbdrive). gpicview gets broken (no loss as I actually like gqview better). mtpaint (depending on original install) may have a lib symlink 'off' .. a re-sym seems to work oki. htop and consoles may behave or display differently from original setups. Puppy Package Manager (petget?.. ah, P417 oem path got changed in the upgrade) wasn't starting from menu or console for me in the P421bb-upgrade (depchecker only shows new installs there, uP476-upgrade shows all). gui for re-X may work once in a dozen tries for me - ctrl+alt+bs is getting to be a habit rather than to even try a button-click. the yaf-splash on left-clicking a mounted-status driveicon (rather than opening a roxfiler window for that drive) is an annoying two-step, imo. Pfind49 (with pfilesearch116) works well
another dumb screenie link, 87k
dotpet compatibility might be iffy (I'm mostly guessing since no pupconn to update PPM and follow the new guidelines for repos & such) for local installs - fresh installs usually work, some even better than previously (like audacious132, as far as I can tell for the simple way I use it). Other simple wms like black and openbox (the newer 3.4.7.2-2 is nice for the menu updating, although I prefer a console fixmenus to the 'quiet' fixmenus from the ob-menu) seem fairly bulletproof. jwm-enhancements help the look (in both since I like the rounded corners, etc and don't use a separate colors file personally)
. . . addenda (htop) . . .
pP417std (out of uP476, upgrade) - htop will not start directly (from menu or wbar), the final -e htop seems to 'flicker' a console window .. works fine from a simple command in an open console
pP417std (out of P421barebones, upgrade) - htop launches as expected
________________________
testing on: i686 machine
processor - Pentium 3 @1GHz
RAM - 512M
vidcard0 - RV280 (aka ATI Radeon 9200), AGP
vidcard1 - not used (switched in BIOS), PCI
soundcard - emu10k1 (aka Creative Audigy 2 ZS or SB0350)
boot/save method - liveCDrw (both upgrades as noted)
limitations - no printer, no internet connection
.. following Flash's lead (somewhat)
1) Burniso2cd of pup4-417-k2.6.30.1.iso to RIDATA 1-4x CD-RW media on DVD-RW IDE1004 unit in P412bone1 (an initial for Xorg, a repeat for Xvesa - both burns 'pinkslipped' by Verify despite proper 4x burn, OK/casebutton-closetray procedure for 1st .. OK did a s/w close of tray on 2nd, just thought I'd try any variation in sequence/procedure to try for a greencard from Verify but sometimes it simply doesn't ). Both actually good.
2) boot 'Xorg' disc with pfix=ram for a peek ... Xorg is still a *mess* to get past for me on my usual machine (I think I guessed lucky .. Mileage May Vary). Leafpad seems a better choice for simple opener of text or at least in openwith (should I edit readmes?). Perhaps make bookmarks to local html like Roxhelps for Pupbrowser (all the wikientries in the world aren't going to help a conn that ain't) - of course one can always play with the url to navigate. Is freetype in? the fonts might be better (quibblequibble). Actually it's quite good for a final(?) alpha as far as a quick look goes in my limited testing. poweroff/nosave.
3) Xvesa (simpler, quicker re-X)
a) started uP476std,Xvesa - this is a fairly mature liveCD tester set up for my comfort and almost entirely stable. gdm-reported disc-size is approx. 237Mb total with 10 savedirs .. switch disc to the 'Xvesa' pP417 and save current session to this disc on poweroff. long-ish 1st "Burning data from previous CD to first track...", then after red "The media tray appears to be open"etc mssg a shorter 2nd burn & autoeject
b) coldboot, both upgrade savedirs then 417's sfs loaded - upgrade successful
4) Xorg
a&b) pretty much the same shutdown, save to switched disc upgrade procedure but used P421barebones,Xorg as the starting liveCD (gdm-reported disc-size approx. 136Mb total with 7 savedirs)
...5) general impressions of both upgrades
Some minor issues even though both successful. A re-install of leafpad may work best if one prefers it to NicoEdit for a simple textviewer/editor (zedit doesn't get 'broken'). SeaMonkey upgrades to 1116 but Medit stayed at earlier 92 version (seems to be fixed with a simple switch of /usr/bin/medit from a renamed click-mounted copy of the liveCD's pup4-417.sfs on thumbdrive). gpicview gets broken (no loss as I actually like gqview better). mtpaint (depending on original install) may have a lib symlink 'off' .. a re-sym seems to work oki. htop and consoles may behave or display differently from original setups. Puppy Package Manager (petget?.. ah, P417 oem path got changed in the upgrade) wasn't starting from menu or console for me in the P421bb-upgrade (depchecker only shows new installs there, uP476-upgrade shows all). gui for re-X may work once in a dozen tries for me - ctrl+alt+bs is getting to be a habit rather than to even try a button-click. the yaf-splash on left-clicking a mounted-status driveicon (rather than opening a roxfiler window for that drive) is an annoying two-step, imo. Pfind49 (with pfilesearch116) works well
another dumb screenie link, 87k
dotpet compatibility might be iffy (I'm mostly guessing since no pupconn to update PPM and follow the new guidelines for repos & such) for local installs - fresh installs usually work, some even better than previously (like audacious132, as far as I can tell for the simple way I use it). Other simple wms like black and openbox (the newer 3.4.7.2-2 is nice for the menu updating, although I prefer a console fixmenus to the 'quiet' fixmenus from the ob-menu) seem fairly bulletproof. jwm-enhancements help the look (in both since I like the rounded corners, etc and don't use a separate colors file personally)
. . . addenda (htop) . . .
pP417std (out of uP476, upgrade) - htop will not start directly (from menu or wbar), the final -e htop seems to 'flicker' a console window .. works fine from a simple command in an open console
pP417std (out of P421barebones, upgrade) - htop launches as expected
________________________
testing on: i686 machine
processor - Pentium 3 @1GHz
RAM - 512M
vidcard0 - RV280 (aka ATI Radeon 9200), AGP
vidcard1 - not used (switched in BIOS), PCI
soundcard - emu10k1 (aka Creative Audigy 2 ZS or SB0350)
boot/save method - liveCDrw (both upgrades as noted)
limitations - no printer, no internet connection
Last edited by `f00 on Tue 04 Aug 2009, 04:00, edited 2 times in total.
pup4-417-k2.6.30.1
Frugal install on CF to IDE adapter
Armada 3500
PII 300mhz
320mb
Netgear WG111T usb wireless
Wifi working well again on the Armada, but no joy at all on a Dell 610 with same dongle (no WPA connection). The only thing I can think of is that the slower USB 1.1 port on the Armada helps, but that's just an ill-informed guess.
Main drive (internal CF) is still showing on desktop as a floppy.
Gparted lists it as a floppy drive too.
Medit: don't know if this is a bug, but clicking 'save' on a new document does not prompt for a file name. The document is just saved as 'F%'
Frugal install on CF to IDE adapter
Armada 3500
PII 300mhz
320mb
Netgear WG111T usb wireless
Wifi working well again on the Armada, but no joy at all on a Dell 610 with same dongle (no WPA connection). The only thing I can think of is that the slower USB 1.1 port on the Armada helps, but that's just an ill-informed guess.
Main drive (internal CF) is still showing on desktop as a floppy.
Gparted lists it as a floppy drive too.
Medit: don't know if this is a bug, but clicking 'save' on a new document does not prompt for a file name. The document is just saved as 'F%'
Set global font size
'Set global font size' does not work.
/usr/sbin/set-xftdpi should be:
/usr/sbin/set-xftdpi should be:
Code: Select all
#!/bin/sh
exec gins /usr/sbin/set-xftdpi.sh /usr/sbin/set-xftdpi.glade
Last edited by shinobar on Sat 01 Aug 2009, 03:29, edited 1 time in total.
Rebooting Ppup-417 after the first session with a just-made pup4save.2fs, AbiWord no longer starts from the desktop icon as on first run but does start from the terminal, as described by Ray MK; the un-antialised fonts (e.g. Times) do not appear in print, nor in print preview or the generated PDF. The terminal window shows error messages when going to print ("(abiword:21199): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated", "** (abiword:21199): WARNING **: could not set the value of Settings.Document.Filter, node not found").
Setting up a printer and actual printing works fine (HP970CXi), will test with other printers.
Aqualung seems really nice, even shows song-related pic beautifully with click-to-enlarge - a pleasant surprise!
Setting up a printer and actual printing works fine (HP970CXi), will test with other printers.
Aqualung seems really nice, even shows song-related pic beautifully with click-to-enlarge - a pleasant surprise!
Having trouble with the PPM and also dir2pet. I made a simple pet (see http://www.murga-linux.com/puppy/viewto ... 608#325608)(that pet has been upgraded with one made in 4.1.2, original posted below) and when it came to the stage of the GUI coming up there was an error and the gui didn't show.
The package was created successfully and does work correctly in other puppies.
With the PPM a menu entry is not being created, this bug was also in the 476 PPM. The package must be reinstalled and even that won't work sometimes, even after a full reboot.
Hope this helps
Edit: original pet attached. Will it show any clues?
Code: Select all
** ERROR **: gtkdialog: Error in line 16, near token '</default>': syntax error
aborting...
cat: /tmp/petspec_db_entry: No such file or directory
With the PPM a menu entry is not being created, this bug was also in the 476 PPM. The package must be reinstalled and even that won't work sometimes, even after a full reboot.
Hope this helps
Edit: original pet attached. Will it show any clues?
- Attachments
-
- Versioninfo.pet
- (571 Bytes) Downloaded 435 times
Puppy Linux Blog - contact me for access
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi,
Tested pup4-417-k2.6.25.16.iso in RAM on PIV Siemens-Fuji 1.5GB Ram
(maybe is this redundant and already well known...sorry if it is)
after saved session to CD-RW, live-cd do not boot
Installed from, and trial to save session to CD-RW :
at end of save I have been asked to place a new CD or to blank the one installed.
It won't boot anymore.
(I tried this 2 times before writing this post - have completely blanked the cd before burning the iso again.)
cheers!
Charlie
Tested pup4-417-k2.6.25.16.iso in RAM on PIV Siemens-Fuji 1.5GB Ram
(maybe is this redundant and already well known...sorry if it is)
after saved session to CD-RW, live-cd do not boot
Installed from, and trial to save session to CD-RW :
at end of save I have been asked to place a new CD or to blank the one installed.
Code: Select all
# disktype /dev/sr0
--- /dev/sr0
Block device, size 127.2 MiB (133343232 bytes)
CD-ROM, 2 tracks, CDDB disk ID 14036402
Track 1: Data track, 121.0 MiB (126906368 bytes)
ISO9660 file system
Volume name "CDROM"
Application "MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CRE ATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING"
Data size 98.73 MiB (103524352 bytes, 50549 blocks of 2 KiB)
El Torito boot record, catalog at 26
Bootable non-emulated image, starts at 27, preloads 2 KiB
Platform 0x00 (x86), System Type 0x00 (Empty)
ISOLINUX boot loader
Track 2: Data track, 6.139 MiB (6436864 bytes)
ISO9660 file system
Volume name "CDROM"
Preparer "XORRISO-0.4.0 2009.06.28.090001, LIBISOBURN-0.4.0, LIBISOFS-0.6 .21, LIBBURN-0.6.7"
Data size 5.809 MiB (6090752 bytes, 2974 blocks of 2 KiB)
# ls /mnt/sr0
2009-07-20-21-40 help.msg isolinux.bin logo.16 vmlinuz
boot.msg initrd.gz isolinux.cfg pup4-417.sfs
(I tried this 2 times before writing this post - have completely blanked the cd before burning the iso again.)
cheers!
Charlie
petget
/usr/local/petget/installpkg.sh at line 240...
Wrong(duplicate '|'):
Should be:
Wrong(duplicate '|'):
Code: Select all
CATEGORY="`cat $DESKTOPFILE | | grep '^Categories=' | cut -f 2 -d '=' | rev | cut -f 1 -d ';' | rev`"
Code: Select all
CATEGORY="`cat $DESKTOPFILE | grep '^Categories=' | cut -f 2 -d '=' | rev | cut -f 1 -d ';' | rev`"
lucent /ager modem on TP disconnects for time out .I am sure its not an ISP problem because few minuted later on 2.16 it works just fine.pup4-417-k2.6.25.16.iso
Puppy built with 2.6.25.16 kernel and lots of modem drivers. Good for older computers and/or if you access Internet via a "winmodem".
if it might help here is some info :
Code: Select all
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
(none) user.warn kernel: ltmodem: module license 'Proprietary' taints kernel.
(none) user.info kernel: Loading Lucent Modem Controller driver version 8.26-alk-8
(none) user.info kernel: Detected Parameters Irq=11 BaseAddress=0x1880 ComAddress=0x0
(none) user.info kernel: ttySLTM0 at I/O 0x1880 (irq = 11) is a Lucent/Agere Modem
(none) user.info kernel: PPP generic driver version 2.4.2
(none) daemon.notice pppd[8443]: pppd 2.4.5 started by root, uid 0
(none) daemon.debug pppd[8443]: using channel 1
(none) daemon.info pppd[8443]: Using interface ppp0
(none) daemon.notice pppd[8443]: Connect: ppp0 <--> /dev/ttySLTM0
(none) daemon.warn pppd[8443]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.debug pppd[8443]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa6208911> <pcomp> <accomp>]
(none) daemon.warn pppd[8443]: LCP: timeout sending Config-Requests
(none) daemon.notice pppd[8443]: Connection terminated.
(none) daemon.notice pppd[8443]: Modem hangup
(none) daemon.info pppd[8443]: Exit.
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi,
Sweep looks to be very attractive (simple, tiny, ...)
I had a look to the sweep users mailing list and subscribed to it...still awaiting confirmation for posting to it.
Seems to have very poor trafic.
http://sourceforge.net/mailarchive/foru ... weep-users
Hop
Hope there is still a pilot in the cockpit...
Cheers
Charlie
EDIT
Yeh...! got subscription confirmation !
and did place a post in swee-users mailing list.
I could then see latest posts dating from january and march 2009.
Will see...
EDIT
about sweep mailing list
it is interesting to read not only the 'users post' but also the 'trackers' ones and attached comments (which in fact are the replies to the post).
Sweep looks to be very attractive (simple, tiny, ...)
I had a look to the sweep users mailing list and subscribed to it...still awaiting confirmation for posting to it.
Seems to have very poor trafic.
http://sourceforge.net/mailarchive/foru ... weep-users
Hop
Hope there is still a pilot in the cockpit...
Cheers
Charlie
EDIT
Yeh...! got subscription confirmation !
and did place a post in swee-users mailing list.
I could then see latest posts dating from january and march 2009.
Will see...
EDIT
about sweep mailing list
it is interesting to read not only the 'users post' but also the 'trackers' ones and attached comments (which in fact are the replies to the post).
Last edited by charlie6 on Sat 25 Jul 2009, 13:32, edited 3 times in total.
SmartLink modem executable update
While exploring the available modem-driver tarballs, I discovered that "slmodem" has recently been updated. For practice, I built it with puppy 4.1.7-k2.6.25.16 and found that only the slmodemd executable has changed. I built it with the "alsa" parameter and replaced it in the slmodem firmware tarball, which is attached.
It has gained about 300KB. The normal version of slmodemd is slightly smaller than the current version, but I concluded the "alsa" version is needed for our ALSA modems.
I tested it with all three types of SmartLink modems and was able to connect to the internet with each.
Thank you, Barry, for including my Linuxant modem package in the upcoming beta. Note that it also supports DGC USB modems. Testing the SmartLink modems in my PC with an HSF modem in it demonstrated that the HSF takes device major numbers that avoid the fixed numbers used by the SL PCI and USB modems when they are present; the HSF may use their numbers otherwise. If both an HSF and SL PCI modem are installed, the HSF will predominate. But if an HSF (PCI) and a SL USB modem are together, the USB modem is selected for use. Per design, a PupDial "probe-ERASE" and reboot are required whenever the modem configuration is changed, in order to re-detect one of the modems.
Richard
It has gained about 300KB. The normal version of slmodemd is slightly smaller than the current version, but I concluded the "alsa" version is needed for our ALSA modems.
I tested it with all three types of SmartLink modems and was able to connect to the internet with each.
Thank you, Barry, for including my Linuxant modem package in the upcoming beta. Note that it also supports DGC USB modems. Testing the SmartLink modems in my PC with an HSF modem in it demonstrated that the HSF takes device major numbers that avoid the fixed numbers used by the SL PCI and USB modems when they are present; the HSF may use their numbers otherwise. If both an HSF and SL PCI modem are installed, the HSF will predominate. But if an HSF (PCI) and a SL USB modem are together, the USB modem is selected for use. Per design, a PupDial "probe-ERASE" and reboot are required whenever the modem configuration is changed, in order to re-detect one of the modems.
Richard
SAS HDD not found !
Hi !
Ubuntu 9.04 found SAS HDD drives but not found in Ppup-417 (pup4-417-k2.6.30.1.iso ).
Thanks,
Ubuntu 9.04 found SAS HDD drives but not found in Ppup-417 (pup4-417-k2.6.30.1.iso ).
Thanks,
[url=http://www.murga-linux.com/puppy/viewtopic.php?t=44675]Hacao Linux 2009 CE released ![/url]
[url=http://hacao.com]Hacao.com[/url] English & Vietnamese !
[url=http://hacao.com]Hacao.com[/url] English & Vietnamese !
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: SAS HDD not found !
Hacao,Hacao wrote:Hi !
Ubuntu 9.04 found SAS HDD drives but not found in Ppup-417 (pup4-417-k2.6.30.1.iso ).
Thanks,
What does "SAS" mean?
Oh, I just looked at the link you posted ...but I still don't know what "serial attached SCSI" means.
[url]https://bkhome.org/news/[/url]
Serial Attached SCSI (SAS). The SAS is a new generation serial communication protocol for devices designed to allow for much higher speed data transfers and is compatible with SATA. SAS uses a mechanically identical data and power connector to standard 3.5" SATA1/SATA2 HDDs, and many server-oriented SAS RAID controllers are also capable of addressing SATA hard drives. SAS uses serial communication instead of the parallel method found in traditional SCSI devices but still uses SCSI commands.
http://en.wikipedia.org/wiki/Serial_Attached_SCSI
Copy files in SAS HDD (35M/s) > SATA HDD (25M/s).
Thanks,
http://en.wikipedia.org/wiki/Serial_Attached_SCSI
Copy files in SAS HDD (35M/s) > SATA HDD (25M/s).
Thanks,
Last edited by Hacao on Fri 24 Jul 2009, 15:53, edited 1 time in total.
[url=http://www.murga-linux.com/puppy/viewtopic.php?t=44675]Hacao Linux 2009 CE released ![/url]
[url=http://hacao.com]Hacao.com[/url] English & Vietnamese !
[url=http://hacao.com]Hacao.com[/url] English & Vietnamese !
Barry's blog
System: BFG NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart 5280 All-in-One, Printer-Scanner-Copier
Doesn't work on this system. It may be related to hardware and does need fixing.shinobar
'Set global font size' does not work
Um, it does work, doesn't need fixing.
System: BFG NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart 5280 All-in-One, Printer-Scanner-Copier
More regarding Linuxant support
Barry,
While working on the Linuxant support, I noticed that Linuxant has patches for the ALSA driver, that appear to add a codec to the module snd-hda-intel.ko, which is in Puppy. I suspect the codec applies to the Conexant HDA modems supported by the ALSA driver.
As the current version of the driver is at 1.0.16, I have attached the patch for that version. However, the driver is now at 1.0.20, and appears to change the snd-hda-intel module so as to move the codecs into separate modules, reducing the snd-hda-intel module from 437K to 40K; I assume only the codec in use (5K-83K) would be loaded with it. That should reduce snd-hda-intel's RAM utilization, when loaded, by at least 314K! In case the latest version of the ALSA driver is chosen for a new Puppy release, I have also included the patch specific to it.
Just something to consider when the time is right.
Richard
While working on the Linuxant support, I noticed that Linuxant has patches for the ALSA driver, that appear to add a codec to the module snd-hda-intel.ko, which is in Puppy. I suspect the codec applies to the Conexant HDA modems supported by the ALSA driver.
As the current version of the driver is at 1.0.16, I have attached the patch for that version. However, the driver is now at 1.0.20, and appears to change the snd-hda-intel module so as to move the codecs into separate modules, reducing the snd-hda-intel module from 437K to 40K; I assume only the codec in use (5K-83K) would be loaded with it. That should reduce snd-hda-intel's RAM utilization, when loaded, by at least 314K! In case the latest version of the ALSA driver is chosen for a new Puppy release, I have also included the patch specific to it.
Just something to consider when the time is right.
Richard
- Attachments
-
- linuxant_hda_codec_patches.tar.gz
- Linuxant ALSA HDA codec patches for alsa-driver 1.0.16 and 1.0.20.
- (21.35 KiB) Downloaded 321 times