)Um, don't know what this means or how to do it - well, I know hot to Ctrl-Alt-Bkspace, but when and where?gcmartin wrote:I have a similar script and this is a problem not just with Slacko, but with other 32bit PUPs as well including lastest WARY. But, not all exhibit this problem.grump wrote: ... If I just want to freeze X, I click on the file in ROX ...
To get around this, requires a Ctrl-Alt-Bkspace in the Live media system.
Me too.ALSO be aware, that this NEVER happens to me when the script is issued from the command line.
On command line it asks for a password = there is none so I press Enter. My current guess is that X is freezing because mount prompts for input but can't get through X.Question to @Grump
When you issue the script on the command line, does the command pause waiting for a password entry?
It has thanks.Hope this helps
What's the point of trying, since you suggested at the outset that it's probably an incompatibility with the cpu? Maybe you should have investigated that fully before casting suspicion on my hard drive, my burner, and my ability to verify a burn.01micko wrote:8-bit wrote:
Hmm. For some reason the BBS has stopped giving me notices of new posts here. I just came to investigate and found a bunch...
-
I don't know how to verify that the disk is as clean as possible. But I've been booting with 2fs files from that same partition with Lupu 5.2.8, and before that, Puppy 4.3.1, a couple of times a day or more, and have never had a boot problem.
Otropogo
I have 3 feelings about your situation.
The first is, is that I have a very similar chipset to the one you describe in my laptop however the PAE (aka RC++) version does not boot as the centrino cpu does not support PAE (yes, a lot of jargon, I will explain more clearly in the release notes. The SMP version may be friendlier).
Second, is there some corruption in your FAT32 partiton? FAT32 is not optimal, but in saying that please be sure that it is clean and that the disk is as clean as possible.
Is Slacko known to be more vulnerable to such "corruption" than Puppy4xx, or lupu 5.2.8? If not, why would it boot fine with them and not with Slacko?
I verified both the downloaded iso and the burn. And the CD has never failed to boot, with or without an xfs file, on the other PC I've used it on. As for the boot device, I boot from it every day with Lupu, and before that with Puppy 4.XX, and have never experienced any such problem.Last, .. you mention being unable to boot correctly from CD (after a successful clean boot). This indicates a problem with the medium or the device.
The only reason I suggest all this is that your problems seem very unique. Testing of Slacko has been ongoing over a number of months and no reports of your issues have surfaced.
That may have something to do with the reception newcomers to this thread receive when they bring problems that are critical and not easily fixable. Considering some of the responses I received, I'm not surprised you haven't heard any such reports.
I hope you can sort it out.
All is well - I've worked what that does, thanks. Much neater than a hard reboot.Um, don't know what this means or how to do it - well, I know hot to Ctrl-Alt-Bkspace, but when and where?.To get around this, requires a Ctrl-Alt-Bkspace in the Live media system.
otropogo wrote:
I verified both the downloaded iso and the burn. And the CD has never failed to boot, with or without an xfs file, on the other PC I've used it on. As for the boot device, I boot from it every day with Lupu, and before that with Puppy 4.XX, and have never experienced any such problem.Last, .. you mention being unable to boot correctly from CD (after a successful clean boot). This indicates a problem with the medium or the device.
Really? Most customers are left happy, if not they are given a full refund. On the other hand, I see there have been flames thrown. Hmm.. let he without sin cast the first flame?otropogo wrote:The only reason I suggest all this is that your problems seem very unique. Testing of Slacko has been ongoing over a number of months and no reports of your issues have surfaced.
That may have something to do with the reception newcomers to this thread receive when they bring problems that are critical and not easily fixable. Considering some of the responses I received, I'm not surprised you haven't heard any such reports.
Intel D865GLC MoBo users? Any? Does this distro work for you?otropogo wrote:What's the point of trying, since you suggested at the outset that it's probably an incompatibility with the cpu? Maybe you should have investigated that fully before casting suspicion on my hard drive, my burner, and my ability to verify a burn.I hope you can sort it out.
Do you really expect new users of your variant to post their inability to boot it when your own first reaction is to try to put a dunce cap on them?
Maybe if you had at least one positive report from someone using Slacko 5.29.6 on an Intel D865GLC MoBo I'd be tempted to keep trying your distro. Do you?
-
slacko-5.29.6-SCSI.iso)
Thanks Stripe.bad news I'm afraid (well for lobster anyway) cannot get openshot 1.4 to compile.
Are you using wbar? Is that available?just took a couple of screenshots of slacko-5.29.5 to show what it can do,
Change your script togrump wrote:On command line it asks for a password = there is none so I press Enter. My current guess is that X is freezing because mount prompts for input but can't get through X.
Code: Select all
#!/bin/bash
mount.cifs //192.168.1.101/DadE /mnt/network/STUDY/DadE -o username=guest,guest
Big claws up from me too.Big Thumbs Up
Maybe swapping a card about may help the issue.The bad eip value is a hardware issue. It may be a NIC problem, or a pci add-on controller issue.
The kernel panics, as it is unable to detect or use the piece of hardware correctly using the base kernel modules. Most likely it is an issue with the kernel being able to set the pci address, or PNP is set in the bios.
Sometimes there is a conflict with another slot, especially in systems that share resources between slots. You used to see this a lot with pci slots next to isa slots, where the resources were shared. Or, a pci slot next to the agp slot. Moving the pci card to another slot might solve the issue, resolving the apparent conflict.
