DSL boots into runlevel 2, problem with ramdisk?
Forum: X and Fluxbox
Topic: DSL boots into runlevel 2, problem with ramdisk?
started by: Koebes
Posted by Koebes on July 26 2006,16:47
Hi,I encountered the following problem:
I need to boot the computer using a boot floppy because the cdrom-drive can't boot. When I use the boot floppy everything's fine until the point when /etc/fstab is created. Then there is an error message saying:
mount: can't find /ramdisk in /etc/fstab or /etc/mtab
The computer continues to boot until it tries to reach runlevel 5, producing error messages connected to the directory /tmp/ramdisk. When the xserver is started, there is an error message saying:
xinit: no such file or directory (errno 2): unable to connect to X server
xinit: no such process (errno 3): server error
Using the fb800x600 boot option doesn't help. If you know what's going on here I'd be very grateful if you gave me a tip, I'm not a great linux wizard, most probably it is an easy mistake I have made. Thanks a lot in advance.
Cheers,
Koebes
Posted by snowyrain on July 29 2006,12:37
Hello,I have the same Problems, can't anybody help?
Greetings
Snowyrain
Posted by jimihieu on Aug. 22 2006,14:39
i got the same problem startin xinit as well after remaster the cd!xinit: no such file or directory (errno 2): unable to connect to X server
xinit: no such process (errno 3): server error
sooo does anyone has any idea why ?
Posted by gigi1234 on Aug. 23 2006,20:26
I am having the EXACT problem too. But this forum doesn't seem particularly active. I'll try posting in some other forums and see what I can find out!
If I can find any info I will post it here for you. Good luck!
Posted by ^thehatsrule^ on Aug. 24 2006,05:41
mount: can't find /ramdisk in /etc/fstab or /etc/mtabThe root of the problem probably starts here... since ~/.xserverrc is executed during the startup of X, but because ~ should be on /ramdisk, this will cause problems.
What happens if you boot with "failsafe"? You may want to try other cheat codes on boot. (see wiki)
Posted by gigi1234 on Aug. 24 2006,11:32
I will try some other cheat codes, but I think it may be a low ram problem. Is this possible?
Posted by ^thehatsrule^ on Aug. 24 2006,23:47
Could be. Try using "lowram" - how much ram do you have?
Posted by gigi1234 on Aug. 25 2006,01:29
yeah trouble is, I have to use fromhd and can't use lowram tooit has 16 MB but I am trying to upgrade to 40 MB. I think X needs 32 to run.
Posted by ^thehatsrule^ on Aug. 25 2006,02:17
I believe previous DSL users have gotten X with 16mb working...Why can't you use both bootcodes at the same time? Multiple cheat codes can be used, separated by a space.
Posted by jimihieu on Aug. 25 2006,02:50
hisorry didnt state clearer earlier...
i get these errors before i get this error:
/etc/rcS.d/S00knoopix-autoconfig: line 536 Read-only filesystem
/etc/rcS.d/S00knoopix-autoconfig: line 560 Read-only filesystem
/etc/rcS.d/S01knoopix-autoconfig: line 160 Read-only filesystem
/etc/rcS.d/S01knoopix-autoconfig: line 162 Read-only filesystem
before i get this error:
xinit: no such file or directory (errno 2): unable to connect to X server
xinit: no such process (errno 3): server error
Does anyone know why pleaes?
thanx
Posted by bkil on Nov. 02 2006,20:55
| Quote (gigi1234 @ Aug. 24 2006,21:29) |
| yeah trouble is, I have to use fromhd and can't use lowram too it has 16 MB but I am trying to upgrade to 40 MB. I think X needs 32 to run. |
Hi there.
Foreword: I've used Firefox on DSL with 32MB of memory, and it runs "okay" if we don't count the minutes of start-up time, but replacing KDrive with a well configured XFree is a must. So you're on the right track with RAM upgrade.
I think I have observed the same 'ramdisk' problem with my P1/16MB config (using Smart Boot Manager), I'll illustrate a basic workaround that I applied at CD boot-time.
| Code Sample |
| /grub\ dsl 2 # make real dirs rm /tmp mkdir /tmp rm /opt mkdir /opt # login home su dsl cd /home/dsl export HOME=/home/dsl startx #or dslinstall #or whatever |
X is hitting swap bad over here with the default settings, but is comfortable after disabling all the eye-candy: opt for the minimal theme, edit .xinitrc (and .desktop) to inhibit xtdesk.sh, fluxter, docked.lua, torsmo, and dillo's automatic startup. You might also see a memory advantage of cutting syslogd from /opt/bootlocal.sh, reducing the number of tty's in /etc/inittab or even tweaking the login shell and startx scripts to use ash. Most included applications perform fair after having done all said. Another advice is to do an uncompressed install, and use a swap partition that resides between your boot and data partition.
One thing I'm still working on, is that the system still operates as slow as if only half of the memory was available, because the caches take no less than 7-9MB... Some tweaking in /proc might help, I hope no kernel recompilation is necessarry.
(An informative note: the X in a full muLinux 14R0 install running on libc5 + kernel 2.0.xx "flies" on a 8-16MB 486.
)Regards,
bkil
Posted by rhpk on Dec. 29 2006,13:02
I post my contribution here in the case of a user getting to this page in search of a solution.BTW, I got the very same problem after burning my own modified copy of DSL. Following the directions in the create_compressed_fs's man page, I created the KNOPPIX file using mkisofs's command line switch "-r".
Unfortunately, that flag mangles the files' permission bits so as to make them more compatible with different systems unable to handle those bits (namely Windows).
Badly enough, this destroys the suid bit of Xvesa (and any other suid program in the KNOPPIX cloop image) making it impossible to start it as dsl user.
The solution is simply use the '-R' flag which preserves that bit.
After that, everything went fine.
Hope this helps.