Quirky 018 feedback
acpi=off & acpi=force
Greetings ,
It is indeed a highly technical subject .
I’ll try to explain , in short , and you’ll understand the difficulty in making compromises .
To start with , its surely not a problem exclusively with Puppy ,
only , other “heavier
It is indeed a highly technical subject .
I’ll try to explain , in short , and you’ll understand the difficulty in making compromises .
To start with , its surely not a problem exclusively with Puppy ,
only , other “heavier
CPU Int Pent EM64T 2X3,4GHz ,2GB ram ,ATI Radeon 9250 ,3x750GB HD
More CUPS ...
Version 4 of the foomatic-rip filter now uses a compiled binary instead of Perl scripts. There is a PET here.
It replaces both /usr/bin/foomatic-rip and /usr/bin/foomatic-rip-gswrapper.
I have tested this in Quirky with a variety of printers that use the foomatic filter and it looks good.
Version 4 of the foomatic-rip filter now uses a compiled binary instead of Perl scripts. There is a PET here.
It replaces both /usr/bin/foomatic-rip and /usr/bin/foomatic-rip-gswrapper.
I have tested this in Quirky with a variety of printers that use the foomatic filter and it looks good.
Thank you very much, TmartinT , for your explanation. This is the first time I've read something I can understand on the topic.
However, I would not necessarily regard an AMD Socket A with a 2GHz+ cpu and an Award BIOS as being "old". [I still play with gifted Skt7/PII/etc) sometimes, but don't necessarily expect them to work, especially with compact liveCD s which require memory that cannot always be fitted/obtained for the oldest boards.]
Notwithstanding, despite your comment, Puppy is the only distro, compact, live or major, that has ever failed shutdown properly on my SiS boards. If you trawl this Forum, however, there seem to be plenty of laptops, even modern ones, that show this feature with Puppy. Personally, I avoid laptops, even gifts, because they are difficult to fix, break easily, have limited upgrade options, use proprietary components and go obsolete before they reach me! But we discussed that earlier...
However, I would not necessarily regard an AMD Socket A with a 2GHz+ cpu and an Award BIOS as being "old". [I still play with gifted Skt7/PII/etc) sometimes, but don't necessarily expect them to work, especially with compact liveCD s which require memory that cannot always be fitted/obtained for the oldest boards.]
Notwithstanding, despite your comment, Puppy is the only distro, compact, live or major, that has ever failed shutdown properly on my SiS boards. If you trawl this Forum, however, there seem to be plenty of laptops, even modern ones, that show this feature with Puppy. Personally, I avoid laptops, even gifts, because they are difficult to fix, break easily, have limited upgrade options, use proprietary components and go obsolete before they reach me! But we discussed that earlier...
I tried seamonkey 1.1.18 pet with mms enabled and it works.rjbrewer wrote:I usually use "about:config" in seamonkey to enable mms streamsSage wrote:Yup, exactly what I found....streams. It would connect to the stream and download data, but, no audio was played.
with various media players, when watching "Delicast.com".
It's not working now; even with a different mplayer.
Maybe a problem with new kernel or new seamonkey?
This is how I enable:
1.) Open Firefox,(Seamonkey) type "about:config" (no quotes anywhere) in the address window, and click enter.
(2.) Right click on the window and choose <New>, then <String> from the pop-up menu that appears.
(3.) In the first pop-up box, enter: "network.protocol-handler.app.mms"
(4.) In the next pop-up box enter the path to gnome-mplayer (e.g. "/usr/bin/gnome-mplayer").
(5.) Now, click in the main window again but choose <New> <Boolean>
(6.) In the first pop-up box, enter: "network.protocol-handler.external.mms"
(7.) In the second pop-up select <True>.
restart the monkey
Will try another 2.04 version later.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
resolv.conf domain line
This isn't necessarily a bug but is curious because it causes resolv.conf toWhat extra stuff do you have in /etc/resolv.conf?
appear as type "data". This doesn't affect my connectivity (wpa2-ath5<>dsl router).
For comparison:
Code: Select all
Lupu005: resolv.conf
# Generated by dhcpcd for interface wlan0
search domain.invalid
nameserver 192.168.254.254
nameserver 192.168.254.254
=================================
Quirky018: resolv.conf
# Generated by dhcpcd from wlan0
# /etc/resolv.conf.head can replace this line
search À D
partview 1.2:
Barry K wrote:
ecube
- Would you mind making a couple more mods?
A "Please wait..." while it's computing for all-drives. Maybe a yaf-splash window.
A "Cancel" button is not appropriate to exit the program. It should be labeled "Ok" or "Quit" or "Exit".
ecube
- Attachments
-
- Partview-1.2.pet
- partview 1.2: Free Space in Drives
- (2.03 KiB) Downloaded 286 times
Last edited by ecube on Mon 12 Apr 2010, 01:36, edited 1 time in total.
acpi=off & acpi=force
Greetings,
@Sage
I didn't meant older MB's ONLY .
It is in fact a combination of factors , and complicated by many choices to be made .
However , problems are more likely with older MB's .
On this "old-timer " (5y) I had troubles to start with .
The original bios code took possession of about 384Kb
low mem , with very bad code . (AMI)
Because the board was delivered with proprietary
binary code ,it was possible to install MS W2000.
XP was install-able , but it crashed so now en then .
That's it , and no USB , NO way to boot from CD or what-
ever .
Even w2000 was limited in its possibilities .
I "flashed" the bios , got a better one on it and could do more. But even now , when I install or run another Linux ,
I have to hack my way trough .
All in all , I new what I was doing , it was the first affordable
MB here , that had support for multiple cpu's at 3.4Ghz
and 800Mhz front speed .
This was a must have for me , normally at times I had a cluster running with 4 PC's . Together they consumed
~2750Wh , this one ~295Wh (CRT monitor 32W included)
For the (apparent) problem in Puppy I would like to ask you
1° Is it possible to track in the forum (or else) what kernel
versions gave that glitch , and with what hardware .
2° Who else in this forum has broken his head on it
It may seem not to be as import end but it really is .
I'm reading for 2 weeks in the forum , and try to find my way
Can't even get to post a comment in Barry's blog on FatDog
I'm refused , security code etc... see link in former post .
From what I read , I understand more or less what
Mr Kauler is aiming at .
Combining newest hardware with the wish to run
on most MB's , AND running all from one file , will be
a challenge indeed I do like challenges , so
From what I 'v learn t , latest Linux kernel development
isn't going to make us happier . There are ~13.000.000
lines of code currently . About 20.000 lines originating from
MS , are posed to be thrown out around 2012 .
Problem is , before that happens , there need to be replacements for it in the kernel .
Linux code tends to be larger (is also better) so ...
Another hard fact is , new hardware demands !
At the other end of the equation , there are more possibilities , to eliminate the need of some BAD bios code.
Reclaiming 64Kb low mem is more valuable than 512Mb
high mem . Probably also allowing older kit back in the game.
Just maybe , some of the tricks in my sleeve might help .
As they say , with some help of your friends
Regards
TmartinT
He who lay down with dogs , shall stand up with flees
Philadelphia Almanack 176?
Benjamin Franklin
@Sage
I didn't meant older MB's ONLY .
It is in fact a combination of factors , and complicated by many choices to be made .
However , problems are more likely with older MB's .
On this "old-timer " (5y) I had troubles to start with .
The original bios code took possession of about 384Kb
low mem , with very bad code . (AMI)
Because the board was delivered with proprietary
binary code ,it was possible to install MS W2000.
XP was install-able , but it crashed so now en then .
That's it , and no USB , NO way to boot from CD or what-
ever .
Even w2000 was limited in its possibilities .
I "flashed" the bios , got a better one on it and could do more. But even now , when I install or run another Linux ,
I have to hack my way trough .
All in all , I new what I was doing , it was the first affordable
MB here , that had support for multiple cpu's at 3.4Ghz
and 800Mhz front speed .
This was a must have for me , normally at times I had a cluster running with 4 PC's . Together they consumed
~2750Wh , this one ~295Wh (CRT monitor 32W included)
For the (apparent) problem in Puppy I would like to ask you
1° Is it possible to track in the forum (or else) what kernel
versions gave that glitch , and with what hardware .
2° Who else in this forum has broken his head on it
It may seem not to be as import end but it really is .
I'm reading for 2 weeks in the forum , and try to find my way
Can't even get to post a comment in Barry's blog on FatDog
I'm refused , security code etc... see link in former post .
From what I read , I understand more or less what
Mr Kauler is aiming at .
Combining newest hardware with the wish to run
on most MB's , AND running all from one file , will be
a challenge indeed I do like challenges , so
From what I 'v learn t , latest Linux kernel development
isn't going to make us happier . There are ~13.000.000
lines of code currently . About 20.000 lines originating from
MS , are posed to be thrown out around 2012 .
Problem is , before that happens , there need to be replacements for it in the kernel .
Linux code tends to be larger (is also better) so ...
Another hard fact is , new hardware demands !
At the other end of the equation , there are more possibilities , to eliminate the need of some BAD bios code.
Reclaiming 64Kb low mem is more valuable than 512Mb
high mem . Probably also allowing older kit back in the game.
Just maybe , some of the tricks in my sleeve might help .
As they say , with some help of your friends
Regards
TmartinT
He who lay down with dogs , shall stand up with flees
Philadelphia Almanack 176?
Benjamin Franklin
CPU Int Pent EM64T 2X3,4GHz ,2GB ram ,ATI Radeon 9250 ,3x750GB HD
- broomdodger
- Posts: 279
- Joined: Sat 10 May 2008, 02:38
- Location: Santa Cruz, CA
IIRC the Sharp PC-PJ2-S2 300MHz Celeron has never shutdown with a Puppy/Quirky.BarryK wrote:Do you get shutdown with an older Puppy?broomdodger wrote:ok, I added acpi=off and shutdown still stops at: System halted.TmartinT wrote:I would try a boot kernel argument : acpi=off
ad this in your grub.conf or menu.lst after the others (if present)
eg : kernel /puppy018/vmlinuz pmedia=atahd pdev1=sda6
psubdir=puppy018 acpi=off
your machine probably doesn't support acpi , so the halt command
goes in a black hole.
I do plan to release a retro build with the 2.6.30.5 kernel, the standard one used in Puppy 431 -- but that doesn't shutdown on all PCs either.
I do not actually USE it, but I do check Puppy/Quirky.
It only has 64MB ram, I cannot find more ram (something special), it is just too slow.
It takes several MINUTES for SeaMonkey to load, although when loaded, it does browse pages.
It has Windows 2000 and Windows does shutdown.
acpi=off & acpi=force
Greetings again,
would you mind sending the content in your grub.conf
or menu.lst ?
your hardware info gives my some thought , however
a real solution will take time and work .
also at start up , try stop the first screen (e.g. with pause
or esc , maybe other key , not standardized ! )
then , you can find some notion about BIOS , possible
other info .
Send these , and I'll search further on them .
Regards,
TmartinT
He who lays down with dogs , shall stand up with flees
Philadelphia Almanack 176?
Benjamin Franklin
would you mind sending the content in your grub.conf
or menu.lst ?
your hardware info gives my some thought , however
a real solution will take time and work .
also at start up , try stop the first screen (e.g. with pause
or esc , maybe other key , not standardized ! )
then , you can find some notion about BIOS , possible
other info .
Send these , and I'll search further on them .
Regards,
TmartinT
He who lays down with dogs , shall stand up with flees
Philadelphia Almanack 176?
Benjamin Franklin
CPU Int Pent EM64T 2X3,4GHz ,2GB ram ,ATI Radeon 9250 ,3x750GB HD
- broomdodger
- Posts: 279
- Joined: Sat 10 May 2008, 02:38
- Location: Santa Cruz, CA
Re: acpi=off & acpi=force
# GRUB configuration file '/boot/grub/menu.lst'.TmartinT wrote:would you mind sending the content in your grub.conf or menu.lst ?
# generated by 'grubconfig'. Mon Sep 21 11:24:28 2009
#
# The backup copy of the MBR for drive '/dev/sda' is
# here '/boot/grub/mbr.sda.18185'. You can restore it like this.
# dd if=/boot/grub/mbr.sda.18185 of=/dev/sda bs=512 count=1
#
# Start GRUB global section
timeout 4
color light-gray/blue black/light-gray
# End GRUB global section
#
title Win2k
rootnoverify (hd0,0)
makeactive
chainloader +1
#
title Linux 018
rootnoverify (hd0,1)
kernel /quirky018/vmlinuz pmedia=atahd psubdir=quirky018 nosmp acpi=off
initrd /quirky018/initrd.gz
#
Do you want me to enter BIOS? It is F2 (fairly common).TmartinT wrote:also at start up , try stop the first screen (e.g. with pause or esc , maybe other key , not standardized ! ) then , you can find some notion about BIOS , possible other info .
What would you like me to check?
- broomdodger
- Posts: 279
- Joined: Sat 10 May 2008, 02:38
- Location: Santa Cruz, CA
I missed this post, but now changed to acpi=force... and it shutdown!Sage wrote:Many moons ago, we (Dougal) established that:broomdodger wrote: I added acpi=off
acpi=force
was the standard workaround for misbehaving Puppy shutdowns. It happens with SiS 735 & 748 as well as a plethora of laptops. However, it is a just a workaround not a solution.
ok, a workaround... any solution in sight?
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
What date does the BIOS have? You should see that during bootup, or run the BIOS setup. Puppy does have a utility that will display all sorts of info about the BIOS -- but I can't recall its name right now.broomdodger wrote:I missed this post, but now changed to acpi=force... and it shutdown!Sage wrote:Many moons ago, we (Dougal) established that:broomdodger wrote: I added acpi=off
acpi=force
was the standard workaround for misbehaving Puppy shutdowns. It happens with SiS 735 & 748 as well as a plethora of laptops. However, it is a just a workaround not a solution.
ok, a workaround... any solution in sight?
The kernel is configured not to use acpi for any BIOS dated prior to January 2001. Which might account for your problem.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
mms audio streaming is "working" for me:
http://bkhome.org/blog/?viewDetailed=01502
...can you guys who have the problem please run 'pupradio' from a terminal and post the messages?
http://bkhome.org/blog/?viewDetailed=01502
...can you guys who have the problem please run 'pupradio' from a terminal and post the messages?
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Right-click the retrovol icon to bring up the mixer, see if there is another level adjustment that will work.pri wrote:anyone here play music with quirky ? i cant control the volume with retrovol,
retrovol work on 431 but not on quirky 1.8 or 431 build with last woof.
[url]https://bkhome.org/news/[/url]
- broomdodger
- Posts: 279
- Joined: Sat 10 May 2008, 02:38
- Location: Santa Cruz, CA
1998BarryK wrote:What date does the BIOS have? You should see that during bootup, or run the BIOS setup. Puppy does have a utility that will display all sorts of info about the BIOS -- but I can't recall its name right now.broomdodger wrote:I missed this post, but now changed to acpi=force... and it shutdown!Sage wrote: Many moons ago, we (Dougal) established that:
acpi=force
was the standard workaround for misbehaving Puppy shutdowns. It happens with SiS 735 & 748 as well as a plethora of laptops. However, it is a just a workaround not a solution.
ok, a workaround... any solution in sight?
The kernel is configured not to use acpi for any BIOS dated prior to January 2001. Which might account for your problem.
Is there any way to pause the display to read all.
PupRadio audio
PupRadio works fine for me running Quirky 018 off CD.
I did have to play with settings in gnome-mplayer to get it to work for PupRadio.
The main problem was the cache size was too high and it would take a long time for the cache to fill before gnome-mplayer would output sound.
I set cache to 32K and at start, instant sound.
I did have to play with settings in gnome-mplayer to get it to work for PupRadio.
The main problem was the cache size was too high and it would take a long time for the cache to fill before gnome-mplayer would output sound.
I set cache to 32K and at start, instant sound.