Posted: Fri 14 Oct 2011, 06:46
Hi 8-bit
It should show blue when AC is plugged, red when unplugged.. working ok here.
It should show blue when AC is plugged, red when unplugged.. working ok here.
Code: Select all
Section InputDevice
Identfier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbMode1" "pc102"
Option "XkbLayout" "be" "#xkeymap0
No, it's not part of the problem. I called it a 2fs file out of habit, and because I hadn't actually looked at the extension. How could a 3fs file get a 2fs extension unless one renamed it manually? In any case, now that I've looked at it (having created a second save file, this one a "2fs"), I can assure you that both have the original extension Slacko gave them. And both of them cause it to seize up on reboot, whereas there's no such problem booting with pfix=ram.8-bit wrote:As per your statement of saving to an ext3 slacksave file, you keep calling it a 2fs file. If you saved it as a 3fs file it should have a 3fs extension and not a 2fs file extension.
I think that may be part of your problem if the slacosave file has the wrong extension.
Such a long-winded way of gratuitously calling someone "stupid". Your reasoning is defective...I jumped through a few hoops getting slacko rc working for me. But it seems that if I can do it, you should also be able to.
If I was setting at your PC, I and most others here could most likely get it to work to.
I'm looking at it (all 32MB of it) sitting right beside the original 512MB 3fs file on my hard drive.As a for instance, you state creating a 32meg slacksave file.
32megs is not even an option for size of it.
Oh, you mean I should ignore the specific recommendation to do so?You already stated you can boot from the CD to a desktop with all icons present and menu items present also.
But you just might be trying to install too many things before creating a save file.
Have you tried booting from the CD with "puppy pfix=ram" and setting up the bare minimums.
Do not at that time try to install flashplayer.
I suggest you direct your suggestions to those (if they exist) who are handling the documentation for Slacko. As for your assurance that perseverance will end in success - it's both illogical and irrelevant. I'm not interested in testing my ability to work around basic functionality issues in a new OS, much less to prove that I'm as smart as you and "most others".You can do that after a reboot.
There is an item in the menu to do that.
Also, do not go with less than a 512 meg save file.
Ext2 or ext3 is fine, but the save file should have a 3fs filename extension if you pick ext3 and a 2fs filename extension if you pick ext2.
Persevere, and you will succeed.
Hi 01micko still can't get this to act properly. appreciate any ideas.jim3630 wrote:01micko yes a problem I reported in prior betas.01micko wrote:Was this a problem in any of the betas? If not I have a possible fix. Let me know please before I post it. Thanks.jim3630 wrote:01micko,
this problem is beyond my skill level and looks like it is not my hardware since in other pups once the speakers are chosen via multi-sound card wizard on reboot sound continues to go to those speakers. have looked in other pups multi-sound card wizard and the choices are the same as in the pic of my first post here in RC. any ideas?
Code: Select all
EXT2-fs (sda6): error: ext2_get_inode: unable to read inside inode block_inode=328005, block=1343490
Most of the time, I press the power button and it will try to start but immediately die. It will then refuse to do anything for ages. Every now and again it will actually start up and be usable. The current PSU is out of an old machine from work. TBH I suspect it's not powerful enough for everything in the box.Sage wrote:'pretty much' - what does that mean? Either it's dead or not?power supply has pretty much had it.
Even if I was willing to poke around in a power supply containing potentially nasty voltages, I'd be unlikely to know what I'm looking at.Sage wrote:If it needs cleaning just hose it and dry it + lube the fan. If it's dead, check the caps for bulges, fuses for continuity and varistors. Rarely anything else in a PSU.
Thanks for the offer, but I have no problem affording a replacement. I just haven't got round to it as I've been very busy recently and it isn't a priority machine.Sage wrote:Whatever, please edit your profile to show your location. If you are in the UK I can probably offer you a replacement, gratis.
Yes, that's how I run linux on all of my machines.8-bit wrote:otropogo,
...
From what I understand so far, you are booting from CD and without installing Puppy, you are just setting things up and creating a save file on a fat partition when asked on rebooting if you want to make one.
As I described previously, the display indicates that the save file is loaded and that the sfs file is copied to RAM. As I also mentioned, the point at which the display freezes is different on every boot, as are the lines displayed.Then after the save file is created and the reboot with the CD occurs, a save file is searched for and if found, loaded into memory and then the slacko SFS is loaded.
So when you boot, are you seeing that the save file is loaded first?
Do you see then the slacko sfs file is then loaded?
I am trying here to figure out at what point the boot errors out in the booting process.
If I have this right so far, chime in.
I didn't time this exactly, but nothing more appeared for at least four minutes, so I conclude the system was locked up.updating
loading kernel modules...
OTOH I used the same CD to boot on another system, the one I'm using right now, save a 512MB 3fs file to the hard drive, and rebooted without incident using that file.Updating
loading kernel modules...[107.636962] BUG:unable to handle kernel.
Your obnoxious remark is misdirected.tasmod wrote:Wow otropogo, you sure go out your way to make friends and influence people don't you !
How so? The posters who write gratuitous insults and misinformation publicly are going to turn miraculously into gracious correspondents and precious sources of information via Private Messaging?jim3630 wrote:otropogo, I have been where your at with software and people that just won't work right.
think everyone here gets your frustrated. pms instead of open posts may get you better results.
Does it make sense to you that it would boot and run fine from the LiveCD?8-bit wrote:otropogo,
I think we might be getting somewhere after the line you saw that said
"loading kernel modules...[107.636962] BUG:unable to handle kernel."
It just may be that the kernel in the version you downloaded is incompatible with that PC. I do not think saving to an NTFS vs VFat formatted partition should make any difference.
There are two kernel versions of Slacko and it just may be that that particular PC may require the other kernel version.
If we can get 01micko to chime in here, he may be able to shed some light on that part.
If you're seriously trying to run Slacko with a 32MB Pupsave, that's the cause of your problem right there. I can use that up on a pfix=ram start just by downloading the MESA graphics driver (20MB) and the Flash Player (about 12MB?).otropogo wrote:I'm looking at it (all 32MB of it) sitting right beside the original 512MB 3fs file on my hard drive.
I'm not being particularly bright today, sorry. Is your problem that Slacko boots fine from a pfix=ram situation but attempting a normal boot from a pupsave is failing? Could be that for some reason the system isn't creating a functioning save file - I've seen this before myself while testing with the Lucid branch.otropogo wrote:Does it make sense to you that it would boot and run fine from the LiveCD?