I have finally made X Windows work booting from a compressed file system.
It didn't work when the whole filesystem was in memory (although it was readwrite).
It works when the file system is is memory EXCEPT /var and /tmp, which are now in a
read-write disk partition.
Isn't it strange?
Although it works now, it would be great if someone could tell me why it does, or why
it didn't before.
Thanks
--
Carlos Mateo
[EMAIL PROTECTED]
-----Mensaje original-----
De: Mateo Garcia, Carlos
Enviado el: lunes, 11 de marzo de 2002 13:20
Para: Xpert
Asunto: [Xpert]Error starting X
I have an embedded system with X windows, and it works OK.
Now I try to compress the whole filesystem and boot with this image as initrd.
I am using LILO, and my lilo.conf looks looks:
....
image = /embedded/boot/bzImage
ramdisk =10000
label = embedded
root = /dev/hda3
image = /embedded/boot/bzImage
ramdisk = 10000
label = embeddedRD
initrd = /embedded/rootfs.gz
root = /dev/ram0
....
"rootfs.gz" is /dev/hda3 but compressed. There is no linuxrc, so the only thing the
initrd does is decompress rootfs.gz into /dev/ram0 and then mount it as root.
Everything works fine, except X Windows. When I execute startx, I get these errors:
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
...
giving up.
xinit: No such file or directory (errno = 2): unable to connect to X server
xinit: No such process (errno = 3): Server error
I have compared the root filesystems resulting from booting "embedded" and
"embeddedRD" and I see no difference.
Any hint how to solve this??
Thank you.
--
Carlos Mateo
[EMAIL PROTECTED]
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
