[Cooker] Permission problems and missing files
Starting gnome+metacity/windowmaker takes forever and leaving gnome-session takes even longer time. Also all xterms and gnome-terminals pop up when started or from saved state but no prompt appear :( On the maximum I can get one xterm and sometimes one gnome-terminal to use on the whole desktop! I suppose the problem is the access setup to the applications and suspect msec. Currently my msec level is 3. Very annoying indeed. The .wmaker-session-errors file says when trying first to open an xterm, and then a gnome-panel under wmaker: Terminal: Error 18, errno 13: Permission denied Reason: spawn: open() failed on ptsname Terminal: Error 18, errno 13: Permission denied Reason: spawn: open() failed on ptsname Unable to open desktop file file:///var/lib/gnome/Mandrake/Configuration/Configure%20your%20computer.desktop for panel launcher: Error reading file 'file:///var/lib/gnome/Mandrake/Configuration/Configure%20your%20computer.desktop': File not found
Re: [Cooker] Re: Problems booting with ext3 for root partition
Finally a kernel that boots with initrd and ext3 as a module: 2.4.22.25mdk. Thanks, no noinitrd kernel option needed anymore! On Thu, 2003-11-06 at 13:46, Stew Benedict wrote: On Thu, 6 Nov 2003, Duncan wrote: Svante Signell posted [EMAIL PROTECTED], excerpted below, on Thu, 06 Nov 2003 09:12:23 +0100: The long thread on 'kernel 23mdk panic' seems to be related to my problem. Has anyone made a summary of conclusions made so far? Which kernels are known to boot properly, with and without initrd? I compile my own kernel from kernel.org sources, so haven't been following this real closely, but AFAIK, any of the Mdk kernels work if ext3 support is compiled directly into the kernel, rather than as a module. I haven't been following it closely enough to know which kernels work with ext3 as a module. with or without user recompilation. That's not the whole story: [EMAIL PROTECTED] stew]$ /sbin/lsmod | tail -2 ext3 60048 2 jbd39296 2 [ext3] [EMAIL PROTECTED] stew]$ uname -r 2.4.22-23mdk / is ext3, booting with an initrd single disk, / is hda5, no /boot partition, devfsd=nomount (for LSB) Works for some folks, not others.
[Cooker] Gnome+metacity+msec problems?
Hopefully someone has answers to my questions: 1. How to disable metacity and start sawfish instead, I've seen something like: killall metacity; sleep 5; sawfish, but this does not work. Any hints? 2. Starting gnome+metacity takes forever and leaving gnome takes even longer time. Also all xterms and gnome-terminals pop up when started or from saved state but no prompt appear :( On the maximum I can get one xterm and sometimes one gnome-terminal to use on the whole desktop! I suppose the problem is the access setup to the applications and suspect msec. Currently my msec level is 3. Very annoying indeeed. 3. Disk access seems to be extremely slow on my Linux HDD (/dev/hdb). The first HDD (/dev/hda) has W98 installed and is slower than the second HDD. DMA is enabled and several hdparm settings have been tried, with limited success. I know the fastest HDD should be the boot disk, but this requires some changes of the disks and the boot configurations. How much is the performance hit for this configuration. The second disk is maybe 50-100% faster than the first. Anyway, for example when installing new software with urpmi and rpm, the access to other applications is _very_ sluggish, the system almost stops. Any ideas?
Re: [Cooker] Problems booting with ext3 for root partition
The long thread on 'kernel 23mdk panic' seems to be related to my problem. Has anyone made a summary of conclusions made so far? Which kernels are known to boot properly, with and without initrd? On Tue, 2003-11-04 at 00:06, Svante Signell wrote: Hi, I have been following the cooker development on and off for some years now, and have not had any problems with the root partition as ext3 until around half a year ago. The boot message displayed is: EXT2-fs warning (device ide0(3,65)): ext2_read_super: mounting ext3 filesystem as ext2 This happens with e.g. kernels 2.4.18,2.4.20 and 2.4.22. Also, with an initrd RAM disk no kernels boot at all, the boot halt with a kernel panic, so I have to use the noinitrd option. The master boot record is located on another physical disk (/dev/hda), and I'm using lilo as boot loader. Checking the state with tune2fs -l /deb/hdb1 after boot shows that the filesystem state is not clean. However, booting from a CD and mounting the root partition either as ext3 or ext2, all is OK, the filesystem state is OK. I did even remove all journal file information, checked the partition, created a new journal file (and even tried the features filetype, sparse_super), rechecked again, but same result as before :( What's going on here?
[Cooker] Problems booting with ext3 for root partition
Hi, I have been following the cooker development on and off for some years now, and have not had any problems with the root partition as ext3 until around half a year ago. The boot message displayed is: EXT2-fs warning (device ide0(3,65)): ext2_read_super: mounting ext3 filesystem as ext2 This happens with e.g. kernels 2.4.18,2.4.20 and 2.4.22. Also, with an initrd RAM disk no kernels boot at all, the boot halt with a kernel panic, so I have to use the noinitrd option. The master boot record is located on another physical disk (/dev/hda), and I'm using lilo as boot loader. Checking the state with tune2fs -l /deb/hdb1 after boot shows that the filesystem state is not clean. However, booting from a CD and mounting the root partition either as ext3 or ext2, all is OK, the filesystem state is OK. I did even remove all journal file information, checked the partition, created a new journal file (and even tried the features filetype, sparse_super), rechecked again, but same result as before :( What's going on here?
