PuppyThis forum is for the discussion of Puppy Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After HD install repeating line:
usr/x11r7/bin/xwin: line 35 /tmp/kbdest layout.txt read-only file system
"
"
"
until alt-cntrol-del to reboot
pryer os install was 2.10rc1 move to 2.11 was wire opp.
on the Dell Dimension L500Cx
Distribution: Debian ("jessie", "squeeze"), Linux Mint (Serena), XUbuntu
Posts: 221
Rep:
usr/x11r7/bin/xwin: line 35 /tmp/kbdest layout.txt read-only file system
It's time for "Captain Obvious"!
Your error message means that there was an error on line 35 of a script
called xwin in the /usr/x11r7/bin directory. That is not one of the more
fundamental scripts. I do not know why you have a read-only file system, but
your system is clearly unhappy that it cannot write some configuration file.
My question is if you really need to reboot.
My guess is "Ctrl-C" or "Ctrl-X"
or "Ctrl-Break" should get all of this to stop and maybe get you to a
command line instead of rebooting.
Then you can trouble-shoot from there. You probably should just
re-install Linux, unless you mean that you had a working system and you added
a second hard-drive and you have a new error. Your original message was not
too clear on that.
usr/x11r7/bin/xwin: line 35 /tmp/kbdest layout.txt read-only file system
It's time for "Captain Obvious"!
Your error message means that there was an error on line 35 of a script
called xwin in the /usr/x11r7/bin directory. That is not one of the more
fundamental scripts. I do not know why you have a read-only file system, but
your system is clearly unhappy that it cannot write some configuration file.
My question is if you really need to reboot.
My guess is "Ctrl-C" or "Ctrl-X"
or "Ctrl-Break" should get all of this to stop and maybe get you to a
command line instead of rebooting.
Then you can trouble-shoot from there. You probably should just
re-install Linux, unless you mean that you had a working system and you added
a second hard-drive and you have a new error. Your original message was not
too clear on that.
This is an error in the OS script-it boots and configures form the cd in to puppy but when I install to the HD it will not configure the first time. this was not a problem with version 2:10rc1. The new puppy 2.11 must be locking or not unlocking the file when it installs to the HD. Email Barry about it. This is to see if any other puppy programer can find or reproduce the error.
wscarl,
Your answer is on the forum at the Murga.org website. I can't post the URL because I just joined this forum. Search for kbdextlayout and you will find it. The fix involves a simple script correction. Worked fine for me.
Yes, it's a known install bug in 211. You can boot from the liveCD and edit the startup script that mounts the root file system as read only. To find out which script, search the murga.org forum for "line 54".
I had same problem and i fixed by editing the grub menu list.
boot back into live cd and mount the partition with the hard disk installation, browse to /boot/grub/menu.lidt and change.
kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal
to
kernel /boot/vmlinuz root=/dev/hda1 rw vga=normal
Save & Reboot
Try using some of the boot codes, like acpi=off (or on, or force), noapic, nopcmcia to try to isolate the problem. Do you have an external keyboard connected?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.