Re: [gentoo-user] problem starting KDE
Sorry.. I was not sure if the quoting was right.. gmail just got crazy!! I repeat! On 6/19/05, Holly Bostick [EMAIL PROTECTED] wrote: Not necessarily, if the internal default for this setting is ON (which Idon't know), but in any case, when commented settings revert to theirinternla default, so in this case it might be better to explicitly set it to Off. So I set Option UseFBDev to Off, and now I get this: MergedFB does not work with Option UseFBDev, MergedFB mode is disable. and I'm unable to start X. Well, of course they do-- you're using the 'defaults' option, whichimplies (among other things) 'noexec'-- which means scripts may not be run (no executables may be run) from the partition. You might want toadd the 'exec' option *after* the 'defaults' option (so that itoverrides the 'noexec' included by 'defaults', if you put 'exec' beforedefaults, the 'noexec' witll override the exlplicit 'exec', which is not what you want). You maybe got confused, because 'defaults' use 'exec' and not 'noexec'. But, for clear doubts, I double set 'exec' and tried again, with no success... I still can't create a user properly! And this problem spreads to X startup.. what can be wrong? (from /etc/fstab) /dev/hda5/home vfat defaults,gid=100,umask=002 0 0 I set the gid to all users. I give rxw to 'group' members... but still nothing.. I see a solution by moving /home/ to the linux partition... but I think this should work though...Also not quite sure what is the usefulness of 'umask=000', since that just says leave the umask as it is Yes... it was 002 before.. I changed to check if the problem was due to 'others' permission.. http://www.shell-shocked.org/article.php?id=230 (:: Shell-Shocked ::Tutorial: Multiple Linux Distros). very nice.. :) though, didn't help... :(
Re: [gentoo-user] problem starting KDE
Fernando Meira schreef: Sorry.. I was not sure if the quoting was right.. gmail just got crazy!! I repeat! On 6/19/05, *Holly Bostick* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Not necessarily, if the internal default for this setting is ON (which I don't know), but in any case, when commented settings revert to their internla default, so in this case it might be better to explicitly set it to Off. So I set Option UseFBDev to Off, and now I get this: MergedFB does not work with Option UseFBDev, MergedFB mode is disable. and I'm unable to start X. All right-- I don't know what any of this means, but it is in fact much more information that what we previously had. What in the name of sanity is MergedFB, and where can we turn it off? Why is UseFBDev trying to turn *on* when your setting is *off* ? But in any case, it's time to go back to the sources, clearly. All you've posted is the X.log.0, here are the errors: (WW) The directory /usr/share/fonts/CID/ does not exist. This one is not important (doesn't stop X from starting). (WW) Open APM failed (/dev/apm_bios) (No such file or directory) I don't use APM, as this is a desktop, not a laptop. However, you seem to have a laptop, so while I would not necessarily think that this would stop X from starting (it might, though), this seems distinctly double-plus-ungood and needs to be fixed ASAP in any case. But that's a kernel issue (APM support would seem to be uncompiled). (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled Oh-- *that's* what MergedFB mode is... dual-head! Which you clearly don't even have (unless your second monitor is just broke). So this should be turned off, but still shouldn't be stopping X from starting. The actual showstopper seems to be here: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed [drm] failed to load kernel module radeon (II) RADEON(0): [drm] drmOpen failed (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. Basically, the 'radeon' module (the kernel opensource drivers) are not able to initialize 3D hardware acceleration (afaik, the 'radeon' drivers cannot do this for the Mobility chipsets; you would need the fglrx drivers)-- and if you are using KDM or GDM or Entrance to start X (rather than just 'startx' from a console), you need this functionality (GNOME or KDE, ime, won't start without some form of acceleration, be it ATI, MESA or whatever). So I'd like to know how your kernel is configured, and what your xorg.conf looks like. Well, of course they do-- you're using the 'defaults' option, which implies (among other things) 'noexec'-- which means scripts may not be run (no executables may be run) from the partition. You might want to add the 'exec' option *after* the 'defaults' option (so that it overrides the 'noexec' included by 'defaults', if you put 'exec' before defaults, the 'noexec' witll override the exlplicit 'exec', which is not what you want). You maybe got confused, because 'defaults' use 'exec' and not 'noexec'. But, for clear doubts, I double set 'exec' and tried again, with no success... I still can't create a user properly! And this problem spreads to X startup.. what can be wrong? You're right, according to man mount but I know from hard experience that there is *some* option that sets nodev nosuid and noexec *as well as* the explicit option when you set it ah, it's - user Allow an ordinary user to mount the file system. The name of the mounting user is written to mtab so that he can unmount the file system again. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line user,exec,dev,suid). So I had the wrong option, sorry. But I don't understand why settings in /etc/fstab would affect user creation, or X startup of all things unless what you're saying is: 1) Because your /home partition is FAT32, when you try to create a user, the default files cannot be copied to create the user's home folder because the permissions are wrong. But this doesn't make any sense (to me), because root is creating users, and root *does* have permission; and 2) You cannot start X because your user does not have permission to various files (like .Xauthority), but this also doesn't make sense to me, because a) X is failing to start long before a user is involved (the basic X server is not able to start enough to read user files) and b) the user should have read permissions to their own home folder even if your
Re: [gentoo-user] problem starting KDE
Holly Bostick wrote: All right-- I don't know what any of this means, but it is in fact much more information that what we previously had. What in the name of sanity is MergedFB, and where can we turn it off? Why is UseFBDev trying to turn *on* when your setting is *off* ? For the record, my current xorg.conf device section looks like this: Section Device Identifier Card0 Driver radeon VendorName ATI Technologies Inc BoardName RV350 [Mobility Radeon 9600 M10] Option MergedFB Off Option UseFBDev Off Option MonitorLayout LVDS, CRT Option DynamicClocks On Option EnablePageFlip On Option VGAAcess On Option BIOSHotKeys On EndSection Also, I have *no* DRI section at all...so maybe that needs to be removed or commented out if it is actually causing the fatal error. It is certainly useless Basically, the 'radeon' module (the kernel opensource drivers) are not able to initialize 3D hardware acceleration (afaik, the 'radeon' drivers cannot do this for the Mobility chipsets; you would need the fglrx drivers)-- and if you are using KDM or GDM or Entrance to start X (rather than just 'startx' from a console), you need this functionality (GNOME or KDE, ime, won't start without some form of acceleration, be it ATI, MESA or whatever). Just a clarification here. The radeon driver can provide hardware acceleration on Radeon 9200 and earlier boards (R250 chipsets and below). R300 and above, including mobility, require the fglrx driver for good 3D performance. However the radeon driver fully supports the mobility chipsets for 2D mode (I have Radeon 9600 mobility, M10/R350 chip), which is all that is required for KDM/GDM/and most everything else. 3D screensavers, opengl audio visualizations, and 3D games are the major things that don't run worth a damn with the radeon driver. So I think the problem is in the kernel and X.org configs, for what it's worth. I also think that the radeon driver is the wrong one for you to be using, and you should be using the fglrx driver (check the release notes, but I'm pretty sure it's compatible with the Mobility now). Yes, it will work with my M10 board. But some OpenGL apps still lockup my machine, and you absolutely lose any capability of using software suspend/resume. I happen to consider software suspend more important for my laptop than (broken) 3D support, so I stick with the radeon driver! I also build my system with USE=-opengl, but that is _not_ the problem here. I have a sense that we've got the tiger by the wrong end, but don't have enough information to figure out which end is which :) . I think you are on the right track...it seems to be a conflict between the xorg.conf file, or kernel configuration. But I've tried to duplicate the behavior, with and without dri, with and without the UseFBDev/MergedFB options, and cannot do so. The best I can do is generate errors about failed to open framebuffer device and MergedFB mode disabled. But X still starts. I can't generate any message about failed to load kernel module, or any other messages about the radeon kernel module. Fernando, you may want to try X -configure, which will auto-generate a configuration for you based on the things that X.org detects. You can then test it with X -config /root/xorg.conf.new. This mostly configures things correctly for me, the only thing it gets wrong is that I need /dev/input/mice instead of /dev/mouse in the pointer configuration. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Hi, first of all, thanks for the support! Let me split these into 2 parts: 1) the problem with the X server, and 2) the remaining errors... Although I have a few errors while starting X, they do not make X fail (as I think). After starting X, the problem arises when loading KDE with the following message: -Could not read network connection list. /home/nando/.DCOPserver_nandux__0 Please check that the dcopserver program is running. in the startx.log I get this: kdeinit: Aborting. bind() failed: : Operation not permitted Could not bind to socket '/home/nando/.kde/socket-nandux/kdeinit__0' Warning: connect() failed: : No such file or directory kdeinit: Aborting. bind() failed: : Operation not permitted Could not bind to socket '/home/nando/.kde/socket-nandux/kdeinit__0' Could not register with DCOPServer. Aborting. ERROR: Couldn't attach to DCOP server! This, as I could find until now, is due to problems with my /home partition (fat32). With a new user (with homedir in the linux partition) everything goes fine. For this problem, I can't find solution.. I've tried many mount option with full permission to everyone, but scripts don't run properly (such as useradd and something within the X startup). Now, the errors when starting Xorg: Yes, I think I have conflicts between xorg and the kernel configuration. I've attached my xorg.conf file (the one I adapted after running Xorg -configure I commented the font problem, the DRI section and added some lines in the keyboard and mouse inputs). From what I could see from your xorg.conf, mine got somewhat less detailed :( I'll bring news as soon as possible! As well as the lsmod and dmesg output (they are unavailable to me at the moment of writing this email). For info: I have a ATI Mobility M6 Thanks! On 6/21/05, Richard Fish [EMAIL PROTECTED] wrote: Holly Bostick wrote: All right-- I don't know what any of this means, but it is in fact much more information that what we previously had. What in the name of sanity is MergedFB, and where can we turn it off? Why is UseFBDev trying to turn *on* when your setting is *off* ?For the record, my current xorg.conf device section looks like this:Section DeviceIdentifierCard0Driverradeon VendorNameATI Technologies IncBoardName RV350 [Mobility Radeon 9600 M10]OptionMergedFB OffOptionUseFBDev Off OptionMonitorLayout LVDS, CRTOptionDynamicClocks OnOptionEnablePageFlip OnOptionVGAAcess On OptionBIOSHotKeys OnEndSectionAlso, I have *no* DRI section at all...so maybe that needs to be removedor commented out if it is actually causing the fatal error.It is certainly useless Basically, the 'radeon' module (the kernel opensource drivers) are not able to initialize 3D hardware acceleration (afaik, the 'radeon' drivers cannot do this for the Mobility chipsets; you would need the fglrx drivers)-- and if you are using KDM or GDM or Entrance to start X (rather than just 'startx' from a console), you need this functionality (GNOME or KDE, ime, won't start without some form of acceleration, be it ATI, MESA or whatever).Just a clarification here.The radeon driver can provide hardwareacceleration on Radeon 9200 and earlier boards (R250 chipsets andbelow).R300 and above, including mobility, require the fglrx driver for good 3D performance.However the radeon driver fully supports the mobility chipsets for 2Dmode (I have Radeon 9600 mobility, M10/R350 chip), which is all that isrequired for KDM/GDM/and most everything else.3D screensavers, opengl audio visualizations, and 3D games are the major things that don't runworth a damn with the radeon driver. So I think the problem is in the kernel and X.org configs, for what it's worth. I also think that the radeon driver is the wrong one for you to be using, and you should be using the fglrx driver (check the release notes, but I'm pretty sure it's compatible with the Mobility now). Yes, it will work with my M10 board.But some OpenGL apps still lockupmy machine, and you absolutely lose any capability of using softwaresuspend/resume.I happen to consider software suspend more important for my laptop than (broken) 3D support, so I stick with the radeondriver!I also build my system with USE=-opengl, but that is _not_the problem here. I have a sense that we've got the tiger by the wrong end, but don't have enough information to figure out which end is which :) .I think you are on the right track...it seems to be a conflict betweenthe xorg.conf file, or kernel configuration.But I've tried toduplicate the behavior, with and without dri, with and without the UseFBDev/MergedFB options, and cannot do so.The best I can do isgenerate errors about failed to open framebuffer device and MergedFBmode disabled.But X still starts.I can't generate any message about failed to load kernel module, or any other messages about the radeonkernel module.Fernando, you may want to try X -configure, which will auto-generate aconfiguration for you based on the things that X.org detects.You canthen test it with X
Re: [gentoo-user] problem starting KDE
Fernando Meira wrote: Although I have a few errors while starting X, they do not make X fail (as I think). After starting X, the problem arises when loading KDE with the following message: -Could not read network connection list. /home/nando/.DCOPserver_nandux__0 Please check that the dcopserver program is running. snip This, as I could find until now, is due to problems with my /home partition (fat32). With a new user (with homedir in the linux partition) everything goes fine. For this problem, I can't find solution.. Ah, I think have the answer for this. FAT32 doesn't support 'special' files such as device nodes, fifos, and sockets. That .DCOP... file that KDE needs to create is a socket. The solution for this is to put the users' .kde directories on a filesystem that supports sockets. You might be able to accomplish this through an environment variable, to tell KDE where the users home KDE directory is...search around the KDE documentation for this. You could also use the 'loop' driver to create a filesystem in a file and mount that at ~/.kde. I've tried many mount option with full permission to everyone, but scripts don't run properly (such as useradd and something within the X startup). Well, I have no idea why scripts won't run. Are you sure this is what you mean to say? Can you create your own script and execute it as a user? Sockets, device nodes, etc. I can understand...but not being able to execute any shell scripts is very strange. Now, the errors when starting Xorg: Yes, I think I have conflicts between xorg and the kernel configuration. I've attached my xorg.conf file (the one I adapted after running Xorg -configure I commented the font problem, the DRI section and added some lines in the keyboard and mouse inputs). From what I could see from your xorg.conf, mine got somewhat less detailed :( That is to be expected...I added most of those options by hand. But it should not have configured 'Driver ati', since the ATI driver has no support for 'Radeon' chips. The 'radeon' driver has support for the M6 (Radeon 7000, at least), so I think that line should say 'Driver radeon'. You can just delete all of the commented-out options. For info: I have a ATI Mobility M6 Well, the good news is that the basic driver should give you 3D hardware acceleration. I'm not familiar with the M6/RV100/Radeon 7000 family of adapters, and what the hardware capabilities were. But if the hardware supports 3D, the opensource drivers should as well. But, let's get X started before trying that! -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Hi, On 6/19/05, Holly Bostick [EMAIL PROTECTED] wrote: Not necessarily, if the internal default for this setting is ON (which I don't know), but in any case, when commented settings revert to their internla default, so in this case it might be better to explicitly set it to Off. So I set Option UseFBDev to Off, and now I get this: MergedFB does not work with Option UseFBDev, MergedFB mode is disable. and I'm unable to start X. Well, of course they do-- you're using the 'defaults' option, which implies (among other things) 'noexec'-- which means scripts may not be run (no executables may be run) from the partition. You might want to add the 'exec' option *after* the 'defaults' option (so that it overrides the 'noexec' included by 'defaults', if you put 'exec' before defaults, the 'noexec' witll override the exlplicit 'exec', which is not what you want). You maybe got confused, because 'defaults' use 'exec' and not 'noexec'. But, for clear doubts, I double set 'exec' and tried again, with no success... I still can't create a user properly! And this problem spreads to X startup.. what can be wrong? (from /etc/fstab) /dev/hda5 /home vfat defaults,gid=100,umask=002 0 0 I set the gid to all users. I give rxw to 'group' members... but still nothing.. I see a solution by moving /home/ to the linux partition... but I think this should work thoug... Also not quite sure what is the usefulness of 'umask=000', since that just says leave the umask as it is Yes... it was 002 before.. I changed to check if the problem was due to 'others' permission.. http://www.shell-shocked.org/article.php?id=230 (:: Shell-Shocked :: Tutorial: Multiple Linux Distros). I had a look in there.. very nice.. :) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Fernando Meira wrote: Hi, On 6/19/05, Holly Bostick [EMAIL PROTECTED] wrote: Not necessarily, if the internal default for this setting is ON (which I don't know), but in any case, when commented settings revert to their internla default, so in this case it might be better to explicitly set it to Off. So I set Option UseFBDev to Off, and now I get this: MergedFB does not work with Option UseFBDev, MergedFB mode is disable. and I'm unable to start X. Please fix your mail client to quote properly. Only Holly is going to know which parts of this message she wrote versus which parts you wrote. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
I tried that.. but it didn't solve it. There's a suggestion of re-emerging xorg: echo x11-base/xorg-x11 -minimal /etc/portage/package.use emerge xorg-x11 but from emerge -pv xorg-x11 I realize that this use flag is used by default.. so I assume this would't solve it either.. Having KDE 3.4.1 and 3.3.2 can be a problem? I seem to messed up the instalation and end up with both versions installed :( Any idea? Thanks, FernandoOn 6/18/05, Volker Armin Hemmann [EMAIL PROTECTED] wrote: Hi,shutdown X, than:remove .Xauth, remove all dcop mcop, .ICE* stuff in the home-dir. Remove in /tmp kde-*, mcop*, .X*, .ICE*.try again.--gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Fernando Meira wrote: Hi, I've just merged KDE 3.4.1 (after installing gentoo) following the KDE Configuration HOWTO, but it seems I missed something. Everything works right with root, but I can't start KDE with a user... DCOPserver problem.. This is the output: snip Using vt 7 FATAL: Module radeon not found. [drm] failed to load kernel module radeon The problem is here. My guess is that you have something like the following in your /etc/X11/xorg.conf file: Section Device Identifier Card0 Driver radeon Option UseFBDev On ... EndSection If so, you either need to set UseFBDev to Off, or build your kernel with the radeon frame-buffer driver into the kernel or as a module. If this doesn't help, post the contents of /var/log/Xorg.0.log -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Fernando Meira wrote: On 6/19/05, *Richard Fish* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: If so, you either need to set UseFBDev to Off, or build your kernel with the radeon frame-buffer driver into the kernel or as a module. The UseFBDev is commented.. does that means that is Off ? The default is off, so yes. But I don't understand why you would get a FATAL error from X in that case...but since it seems to be working now, I guess it was something else. While changing this and that, I deleted the /tmp/ by mistake. After creating (mkdir /tmp) and set chmod a+rwx, I got this problem (using the new user): Normal permissions on /tmp are a+rwxt. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Fernando Meira schreef: On 6/19/05, Richard Fish [EMAIL PROTECTED] wrote: If so, you either need to set UseFBDev to Off, or build your kernel with the radeon frame-buffer driver into the kernel or as a module. The UseFBDev is commented.. does that means that is Off ? Not necessarily, if the internal default for this setting is ON (which I don't know), but in any case, when commented settings revert to their internla default, so in this case it might be better to explicitly set it to Off. Anyway, I managed to start KDE. To do that, I created a new user. The difference was that the HOME of my first user is located in a FAT32 filesystem, while I placed the new one is at /tmp/ (ReiserFS). Thus, I would say the problem is with the partition. I also noticed that when creating a new user, the files from /etc/skel are not copied to the users' home-dir. Something is wrong with this partition.. i mount it as follows: /dev/hda5 /home vfat defaults,umask=000 0 0 Both root and users are able to write in that partition, I seems that only scripts fail... Well, of course they do-- you're using the 'defaults' option, which implies (among other things) 'noexec'-- which means scripts may not be run (no executables may be run) from the partition. You might want to add the 'exec' option *after* the 'defaults' option (so that it overrides the 'noexec' included by 'defaults', if you put 'exec' before defaults, the 'noexec' witll override the exlplicit 'exec', which is not what you want). Also not quite sure what is the usefulness of 'umask=000', since that just says leave the umask as it is by default rather than changing it in any way (umask removes permissions from the default settings, which in this case would be something like rw (root), r (root), and r (others), because the default permissions of 777 and 666 have been changed by use of the 'defaults' option). You would probably do better to 1) set the uid= and/or gid= options to give users some ownership rights; 2) change the permissions of the mount point itself to give users some ownership rights; and 3) set an appropriate umask to block rights of others (I was always fond of 007-- all rights for owner who was me, all rights for group which was a custom group to which samba users belonged and no rights whatsoever for others I don't know who these 'others' are, but I don't like em ;-) . You probably want to read 'man mount', but I also wrote a tutorial that discusses managing shared partitions of this nature: http://www.shell-shocked.org/article.php?id=230 (:: Shell-Shocked :: Tutorial: Multiple Linux Distros). Scroll down to The fast explanation of fstab entries for a 'how-tolet' on a successful /etc/fstab entry for vfat partitions. HTH, Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] problem starting KDE
Hi, shutdown X, than: remove .Xauth, remove all dcop mcop, .ICE* stuff in the home-dir. Remove in /tmp kde-*, mcop*, .X*, .ICE*. try again. -- gentoo-user@gentoo.org mailing list
