Hi @ll, Remember the probs I had with a crashing krandrinit when logging in as a normal user? Someone adviced me to check kcmrandrrc in the users home directory for the proper screen resolution. I checked this one, but it already contained the correct values. I tried to add a second set for my second screen but this also didn't solve the crash. Here's my actual kcmrandrrc:
[Display] ApplyOnStartup=true SyncTrayApp=true
[Screen0] height=1024 reflectX=false reflectY=false refresh=89 rotation=0 width=1280
[Screen1] height=864 reflectX=false reflectY=false refresh=92 rotation=0 width=1152
I manually added the section [Screen 1] and below. Locks quite normal, eh? The screen heights and widths are those physically present on my system. Any ideas? Then: Some more quirks and probs I have with my system :-( - A question: How do I permanently enable num lock on the login screen? - I'm having a Compaq DAT Streamer and I try to do backups with the KDAT backup from the archive group. Unfortunately the proggie *never ever* recognises any tape in the streamer. I tried /dev/nst0, /dev/st0 as the tape device name. Though a tape *is* in the streamer KDAT always says "No tape". I also tried /dev/fd0 - just the same. Any idea why the backup doesn't recognize any media? - I'm using CUPS to map a network printer residing on a printer queue of a W2k machine. When mapping the printer I'm giving administrator and its password for authentification at the bill OS machine. Printing then goes fine until I reboot the Linux machine. Obviously CUPS has the old user authentification "forgotten" and tries to use the guest account for printing. Actually I don't want to enable anonymous printing on the windows machine, just because CUPS is too dumb to remember the authentification settings. Any ideas? - From time to time my Logitech USB-Mouse just stops reacting to mouseclicks (but is still movable) If I change to a console and back to KDE the Clicks start working again. - I'm using a Matrox G450 video board. I've downloaded and installed the Linux beta driver from Matrox homepage. So far so good. When I start Matrox' Power Desk to adjust the screen settings it comes up with a box asking for the proper XFConfig. I'm giving the correct path & filename (definitely!) but it still says "Error: The specified file isn't valid. Please make sure the file name refers to a valid configuration file." Any idea why? - I'm trying to test different screen savers to see which one I like best. There seems to be some savers which change screen resolution. Preview of this savers in the screen saver dialog box works fine but as soon as I say "Test" the system badly crashes: First the screen blackens (I suppose it's switching screen res), then it switches back to the old res, then X seems to start again and shortly after that mouse and keyboard freeze without a logonscreen, resulting in a dirty shutdown by having to use reset. If I'm fast enough and I manage to switch to a console during the restart of X I can try to log into a console but the shell isn't starting up. After login I can type characters after characters without ever seeing a prompt. Even Ctrl-Alt-Del is broken. It says it is initiating a shutdown but the system never ever goes down for reboot. Again knock reset before knocking my head on the wall... Any idea? Maybe a problem with the Matrox graphics driver? Any solution? Alota troubles for a kde installation, any help is appreciated! Thx Peter -- No problem is so big that it can't be run away from.
Brockamp@tlt.ilt.fhg.de wrote:
- A question: How do I permanently enable num lock on the login screen?
Using SuSe 9.0, choose "KDE Configuration Centre", then choose "Systemmanager", then "Periferals", then "Keyboard", and check the num-lock option of your choice.
Hi! Hans Rasch <info@icachet.nl> schrieb am 26.03.2004 10:09:42:
Using SuSe 9.0, choose "KDE Configuration Centre", then choose "Systemmanager", then "Periferals", then "Keyboard", and check the num-lock option of your choice.
AFAIK this dialog is for setting the options for an already logged in user, not for the login dialog itself?! Regards Peter
On Friday 26 March 2004 10:04, Brockamp@tlt.ilt.fhg.de wrote:
Hi!
Hans Rasch <info@icachet.nl> schrieb am 26.03.2004 10:09:42:
Using SuSe 9.0, choose "KDE Configuration Centre", then choose "Systemmanager", then "Periferals", then "Keyboard", and check the num-lock option of your choice.
AFAIK this dialog is for setting the options for an already logged in user, not for the login dialog itself?!
Edit kdmrc: NumLock=on The actual place of kdmrc can vary, on my system it is at: /etc/opt/kde3/share/config/kdm/kdmrc but check also /opt/kde3/share/config/kdmrc /opt/kde3/share/config/kdm/kdmrc Cheers, Leen
Leendert Meyer wrote:
On Friday 26 March 2004 10:04, Brockamp@tlt.ilt.fhg.de wrote:
Hi!
Hans Rasch <info@icachet.nl> schrieb am 26.03.2004 10:09:42:
Using SuSe 9.0, choose "KDE Configuration Centre", then choose "Systemmanager", then "Periferals", then "Keyboard", and check the num-lock option of your choice.
AFAIK this dialog is for setting the options for an already logged in user, not for the login dialog itself?!
Edit kdmrc:
NumLock=on
The actual place of kdmrc can vary, on my system it is at:
/etc/opt/kde3/share/config/kdm/kdmrc ...
Maybe you can set this in the BIOS-Options. Regards, Michael -- ____ / / / / /__/ Michael Höhne / / / / / / mih-Hoehne@t-online.de / _____________________________________/
Hi! Michael Hoehne <mih-hoehne@t-online.de> schrieb am 26.03.2004 14:20:19:
Maybe you can set this in the BIOS-Options.
Nope! I already have Num Lock on in the BIOS, but KDE switches it off when starting up... Cheerz Peter
On Friday 26 March 2004 14:20, Michael Hoehne wrote:
Leendert Meyer wrote:
On Friday 26 March 2004 10:04, Brockamp@tlt.ilt.fhg.de wrote:
Hi!
Hans Rasch <info@icachet.nl> schrieb am 26.03.2004 10:09:42:
Using SuSe 9.0, choose "KDE Configuration Centre", then choose "Systemmanager", then "Periferals", then "Keyboard", and check the num-lock option of your choice.
AFAIK this dialog is for setting the options for an already logged in user, not for the login dialog itself?!
Edit kdmrc:
NumLock=on
The actual place of kdmrc can vary, on my system it is at:
/etc/opt/kde3/share/config/kdm/kdmrc ...
Maybe you can set this in the BIOS-Options.
Probably yes, but that was not what Peter wanted. I got no reaction from Peter so I tried it, with 'NumLock=on' in kdmrc: 1) BIOS numlock = off 2) During Graphical login (KDM) numlock = ON 3) In KDE numlock = off Peter, I think this is just what you wanted. Cheers, Leen
Hi @ll, Leendert Meyer <leen.meyer@home.nl> schrieb am 26.03.2004 19:01:16:
Maybe you can set this in the BIOS-Options.
Probably yes, but that was not what Peter wanted.
You're right. I've written that already, BIOS is not the point, as Linux (as most other OS) will set Num Lock on its own.
I got no reaction from Peter so I tried it, with 'NumLock=on' in kdmrc:
1) BIOS numlock = off 2) During Graphical login (KDM) numlock = ON 3) In KDE numlock = off
1) Well, as mentioned, I think BIOS is irrelevant here. 2) is what I was interested in. 3) I want that on, too, but that can be configured from within the normal KDE config panels, found&know that already. I'm a bit slow in replying because I'm a lot away on business and I have to check all settings on my machine at home, means there's no quick testing possible for me, sorry for that. The point why you didn't get any "works"/"works not" reply thus is that I simple didn't find the time to test it yet :-( WIll do it this evening though - hopefully... ;-) Cheerz Peter
On Monday 29 March 2004 12:10, Brockamp@tlt.ilt.fhg.de wrote:
Hi @ll,
Leendert Meyer <leen.meyer@home.nl> schrieb am 26.03.2004 19:01:16:
Maybe you can set this in the BIOS-Options.
Probably yes, but that was not what Peter wanted.
You're right. I've written that already, BIOS is not the point, as Linux (as most other OS) will set Num Lock on its own.
I got no reaction from Peter so I tried it, with 'NumLock=on' in kdmrc:
1) BIOS numlock = off 2) During Graphical login (KDM) numlock = ON 3) In KDE numlock = off
1) Well, as mentioned, I think BIOS is irrelevant here. 2) is what I was interested in. 3) I want that on, too, but that can be configured from within the normal KDE config panels, found&know that already. I'm a bit slow in replying because I'm a lot away on business and I have to check all settings on my machine at home, means there's no quick testing possible for me, sorry for that. The point why you didn't get any "works"/"works not" reply thus is that I simple didn't find the time to test it yet :-(
Well, thanks for replying ;)
WIll do it this evening though - hopefully... ;-)
Yeah, I know ;) Cheers, Leen
Brockamp@tlt.ilt.fhg.de wrote:
Hans Rasch <info@icachet.nl> schrieb am 26.03.2004 10:09:42:
Using SuSe 9.0, choose "KDE Configuration Centre", then choose "Systemmanager", then "Periferals", then "Keyboard", and check the num-lock option of your choice.
AFAIK this dialog is for setting the options for an already logged in user, not for the login dialog itself?!
That's true. It makes so that from the next login on, you'll get the num-lock setting you prefer. I'm not aware of any possibility at the login dialog itself. Maybe someone else?
On Thursday 25 March 2004 17:43, Brockamp@tlt.ilt.fhg.de wrote:
Hi @ll,
- I'm trying to test different screen savers to see which one I like best. There seems to be some savers which change screen resolution. Preview of this savers in the screen saver dialog box works fine but as soon as I say "Test" the system badly crashes: First the screen blackens (I suppose it's switching screen res), then it switches back to the old res, then X seems to start again and shortly after that mouse and keyboard freeze without a logonscreen, resulting in a dirty shutdown by having to use reset. If I'm fast enough and I manage to switch to a console during the restart of X I can try to log into a console but the shell isn't starting up.
Did you try <Ctrl>+<Alt>-<Backspace> to kill X? What's in the logs? Can you login remotely with another PC? If you can, run 'top' prior to testing to see if there is a process going mad (using 100% CPU or memory).
After login I can type characters after characters without ever seeing a prompt. Even Ctrl-Alt-Del is broken.
Edit /etc/sysconfig/sysctl, set ENABLE_SYSRQ="yes" Run SuSEconfig, and reboot. This enables the kernel's "magic key" sequences, see /usr/src/linux/Documentation/sysrq.txt In short: if <Ctrl>+<Alt>-<Del> does not work, you /may/ have now a last resort: Press these sequences in the same order: <Alt>+<SysRq>-<S> ==> S)yncs the disks <Alt>+<SysRq>-<U> ==> U)nmounts the disks <Alt>+<SysRq>-<B> ==> reB)oots (release all keys between sequences) [Germans call <Ctrl>+<Alt>-<Del> 'Affengriffe' (monkeygrip/grab). I wonder how they would call those <SysRq> combinations... ;) ] The SysRq combinations do not always work, but it is best to try them instead of relying on the recovery mechanisms of e.g. the Reiser or Ext3 filesystems.
It says it is initiating a shutdown but the system never ever goes down for reboot. Again knock reset before knocking my head on the wall...
Cheers, Leen
Hi! OK, here's my test results: Leendert Meyer <leen.meyer@home.nl> schrieb am 26.03.2004 20:43:05:
Did you try <Ctrl>+<Alt>-<Backspace> to kill X?
Nope, but tried now. Doesn't work though.
What's in the logs?
Sorry, I'm not that firm in Linux yet ;-( What are the relevant logs for a berserking X?
Can you login remotely with another PC? If you can, run 'top' prior to testing to see if there is a process going mad (using 100% CPU or memory).
Not that easy, as the other machine is Bill OS only (I admit, sigh! Shame on me!) and with my fli4l-router I haven't got the neccessary software on this machine. Is there an easy way to log into a Unix machine from Bill OS? Anyway, I don't think the machine is completely crashed, as from time to time I can still see the HDD-LED signaling a short disk access. It seems more to me that some process has gone berserk, dooming the whole system. Thought this could only Windoze do...
Edit /etc/sysconfig/sysctl, set
ENABLE_SYSRQ="yes"
Run SuSEconfig, and reboot.
Ack. Did that.
This enables the kernel's "magic key" sequences, see /usr/src/linux/Documentation/sysrq.txt
In short: if <Ctrl>+<Alt>-<Del> does not work, you /may/ have now a last
resort:
Press these sequences in the same order:
<Alt>+<SysRq>-<S> ==> S)yncs the disks <Alt>+<SysRq>-<U> ==> U)nmounts the disks <Alt>+<SysRq>-<B> ==> reB)oots
(release all keys between sequences)
Tried it. Doesn't work either :-(
[Germans call <Ctrl>+<Alt>-<Del> 'Affengriffe' (monkeygrip/grab). I wonder how they would call those <SysRq> combinations... ;) ]
Hm, good question! I could only tell you the english nick for the 'Affengriff', INMHO also a nice one: It's Vulcan-nerve-pinch ;-) Anyone an idea for SysRq-combinations? How about 'Gorillagrab', as you have to spread your fingers even wider?
The SysRq combinations do not always work, but it is best to try them instead of relying on the recovery mechanisms of e.g. the Reiser or Ext3 filesystems.
Yep, that's right. Luckily until today my transaction FS fell on its feet every time I had to shotgun the machine. Cheerz Peter -- Mr. Worf, lock a tractor beam on that Tagline and bring it in.
On Tuesday 30 March 2004 12:31, Brockamp@tlt.ilt.fhg.de wrote:
Hi!
OK, here's my test results:
Leendert Meyer <leen.meyer@home.nl> schrieb am 26.03.2004 20:43:05:
Did you try <Ctrl>+<Alt>-<Backspace> to kill X?
Nope, but tried now. Doesn't work though.
What's in the logs?
Sorry, I'm not that firm in Linux yet ;-( What are the relevant logs for a berserking X?
/var/log/XFree86*.lo If there are more then one, check the date. Lines starting with "(EE)" indicate an error (grep "^(EE)" XFree86*.log). Maybe there's also something in /var/log/messages. Each log entry has a timestamp, so errors should be easy to locate. Don't post the whole files, only those lines that contain errors, and perhaps a some lines of relevant context.
Can you login remotely with another PC? If you can, run 'top' prior to testing to see if there is a process going mad (using 100% CPU or memory).
Not that easy, as the other machine is Bill OS only (I admit, sigh! Shame on me!) and with my fli4l-router I haven't got the neccessary software on this machine. Is there an easy way to log into a Unix machine from Bill OS?
Yes! :) PuTTY. Very small, quite easy. Get it here: http://www.chiark.greenend.org.uk/~sgtatham/putty/ It's an exe program, you could run it even strait from there. If you want to check the MD5sums: copy putty.exe and md5sums to the same directory /on a Linux machine/, and issue "md5sum -c md5sums". There should be a message indicating putty.exe is OK. Before trying a screensaver, login with putty and start 'top'. [...]
Press these sequences in the same order:
<Alt>+<SysRq>-<S> ==> S)yncs the disks <Alt>+<SysRq>-<U> ==> U)nmounts the disks <Alt>+<SysRq>-<B> ==> reB)oots
(release all keys between sequences)
Tried it. Doesn't work either :-(
You could try it once to see if it works. The safest way to try is boot the machine in runlevel S: At the boot prompt (the first prompt after passing the BIOS screens) just type an 'S' (no quotes) and hit enter. The system boots in a special maintenance mode. Only / (and perhaps /boot) is/are mounted. Nice is they're mounted read only, meaning you can't damage the file system! :) Now try the SysRq sequences as indicated above: while holding down <Alt>+<SysRq> press the 'S' key, etc. Doesn't work? Just reboot normaly. If the SysRq sequences don't work during the screensaver crash, It's probably best to just leave those alone. An unclean reboot (when disks are not unmounted prior to halting/booting) could damage the file system, with even a (very small) risk to be forced to re-install Linux, but a bit more likely resulting in damaged files. You're a bit better off if you use reiserfs or ext3. A simple 'mount' command will tell you that. Decide if you want to continue. ;) BTW, YaST should indicate if there are missing/conflicting packages. If so, try to solve them, or post the missing/conflicting packages here. Cheers, Leen
participants (4)
-
Brockamp＠tlt.ilt.fhg.de -
Hans Rasch -
Leendert Meyer -
Michael Hoehne