Re: [newbie] login problem
Derek Jennings wrote: On Sunday 13 February 2005 20:37, Chuck MATTSEN wrote: Hey, Derek ... I've also done as you suggest above in switching to udev, but at boot I'm getting a lot of error messages reading: open /dev/fb0: No such file or directory Is there something else that must be tweaked? I've changed each instance of devfs=mount to devfs=nomount, have run lilo -v, and have checked in services running, where devfs is shown as not running, not to start at boot and udev is shown as running, to start at boot ... What am I missing here? Log-in is now lightning fast in comparison, of course, but still a long string of those errors during both boot and shutdown. ...? /dev/fb0 is the video frame buffer. That node is present on my system, but for some reason it is not being created on yours. Are you up to date with your updates? Maybe it would help if you created it manually. Try putting mknod /dev/fb0 c 29 0 at the end of /etc/rc.local Hmmm. No effect, at least upon the boot-up error messages after doing so. I /did/ get some interesting visual effects at shutdown time, but other than that, no noticeable difference. Thanks, will have to research it some more. It wouldn't appear to be critical, at least, as all seems normal otherwise. -- Chuck MATTSEN / [EMAIL PROTECTED] / Mahnomen, MN MT Lookup: http://eot.com/~mattsen/mtsearch.htm Registered Linux User #346519 Random Thought/Quote for this Message: A fanatic is a person who can't change his mind and won't change the subject. - Winston Churchill Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] login problem
On Sunday 13 February 2005 20:37, Chuck MATTSEN wrote: > Derek Jennings wrote: > > This is possibly because you upgraded instead of installing. You are > > still using devfs instead of udev. > > > > To fix it. > > Install udev > > Edit /etc/lilo.conf and in each stanza in the 'append' line change the > > devfs option to 'devfs=nomount' > > > > Then run 'lilo -v' to rewrite your boot sector. > > Then reboot. > > During the boot sequence you should see a message about using udev. > > > > Thats it! Your log in should now be much faster. > > Hey, Derek ... I've also done as you suggest above in switching to udev, > but at boot I'm getting a lot of error messages reading: > open /dev/fb0: No such file or directory > > Is there something else that must be tweaked? I've changed each instance > of devfs=mount to devfs=nomount, have run lilo -v, and have checked in > services running, where devfs is shown as not running, not to start at boot > and udev is shown as running, to start at boot ... > > What am I missing here? Log-in is now lightning fast in comparison, of > course, but still a long string of those errors during both boot and > shutdown. ...? /dev/fb0 is the video frame buffer. That node is present on my system, but for some reason it is not being created on yours. Are you up to date with your updates? Maybe it would help if you created it manually. Try putting mknod /dev/fb0 c 29 0 at the end of /etc/rc.local derek -- www.jennings.homelinux.net http://twiki.mdklinuxfaq.org Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] login problem
Derek Jennings wrote: This is possibly because you upgraded instead of installing. You are still using devfs instead of udev. To fix it. Install udev Edit /etc/lilo.conf and in each stanza in the 'append' line change the devfs option to 'devfs=nomount' Then run 'lilo -v' to rewrite your boot sector. Then reboot. During the boot sequence you should see a message about using udev. Thats it! Your log in should now be much faster. Hey, Derek ... I've also done as you suggest above in switching to udev, but at boot I'm getting a lot of error messages reading: open /dev/fb0: No such file or directory Is there something else that must be tweaked? I've changed each instance of devfs=mount to devfs=nomount, have run lilo -v, and have checked in services running, where devfs is shown as not running, not to start at boot and udev is shown as running, to start at boot ... What am I missing here? Log-in is now lightning fast in comparison, of course, but still a long string of those errors during both boot and shutdown. ...? -- Chuck MATTSEN / [EMAIL PROTECTED] / Mahnomen, MN MT Lookup: http://eot.com/~mattsen/mtsearch.htm Registered Linux User #346519 Random Thought/Quote for this Message: Any sufficiently advanced technology is indistinguishable from magic. -- Arthur C. Clarke, "Technology and the Future" Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] login problem
On Sunday 13 February 2005 11:20, Mr Steve Harris wrote: > Hello, > My son recently installed Mandrake 10.1 over 9.2 on my > machine. While most things seem to be going smoothly, > sometimes it takes a long time to log in. > > The machine has a p3 and 256MB RAM. > > It gets to the GUI login screen. I log in, but it > then sits there and does nothing for sometimes over 10 > minutes. It does it for other users as well, using > both KDE and Gnome. It doesn't do it all the time, > nor can I see a pattern. > > Can anyone help? > > Steve. > > Find local movie times and trailers on Yahoo! Movies. > http://au.movies.yahoo.com This is possibly because you upgraded instead of installing. You are still using devfs instead of udev. To fix it. Install udev Edit /etc/lilo.conf and in each stanza in the 'append' line change the devfs option to 'devfs=nomount' Then run 'lilo -v' to rewrite your boot sector. Then reboot. During the boot sequence you should see a message about using udev. Thats it! Your log in should now be much faster. HTH derek -- www.jennings.homelinux.net http://twiki.mdklinuxfaq.org Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
[newbie] login problem
Hello, My son recently installed Mandrake 10.1 over 9.2 on my machine. While most things seem to be going smoothly, sometimes it takes a long time to log in. The machine has a p3 and 256MB RAM. It gets to the GUI login screen. I log in, but it then sits there and does nothing for sometimes over 10 minutes. It does it for other users as well, using both KDE and Gnome. It doesn't do it all the time, nor can I see a pattern. Can anyone help? Steve. Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
[newbie] login problem with 8.1
Hi all, I am having a small problem, recently I installed 8.1 on a box, and installed 2.4.12-5 kernel.. all went well. So anyway, I started by using msec to increase security to high.,.. and started opening all the stuff that I needed. then I added amavis and started setting it up as a server.. then I thought I should restart it,, when I did, I get the login screen, (console not x) and when I try to log in, it tells me who the last login was (me) but won't go to a prompt. so I booted rescue, and changed msec to 3 and then 2, both to no avail. I can't log in,, I also changed all the passwords and tried to log in again, no difference.. I am abit lost here, anyone have any suggestions.. neither root or my user account will login ... which suggests its not a password issue.. any help would be much appreciated. rgds Frank === Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] login problem
first, you must disable the USB support in your BIOS, even if you do not have a USB device or even the ports external to your computer box, since the mother board might still support it and want to be ready should you ever do plug in a USB device. second, it may be that you need to hit "apply" then OK. [I just learned that in Kmail after spell checking, if I hit cancle (since i did not want to spellcheck the quoted part) the corrected words went back to the way they were before i spellchecked.] I would recomend to turn off kudzu as a startup service, and next would be to insure that plug and pray aware OS is set to OFF in BIOS. On Monday 30 July 2001 09:14, Charlie Oriez wrote: > On Saturday 28 July 2001 12:46, Frans Ketelaars wrote: > > [frans@localhost frans]$ cat /etc/modules.conf | grep 180 > > alias char-major-180 usb-ohci > > > > so it seems to have something to do with USB. > > > > The "Can't locate module ..." means just that: modprobe cannot find > > the module, it does not exist or it's in the wrong place. > > > > [frans@localhost frans]$ locate usb-ohci > > /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz > > > > Note the kernel version in the path. > > > > cat /proc/devices says char-major-4 is associated with ttyS. > > Maybe something with the keyboard? > > > > Sorry I have no solution just information. > > > > -Frans > > Interesting. > > I have no USB ports on the machine, or so I believe (see below) and the > installation should have detected that. > > I get a fail at boot time as services are being started when attempting to > detect the USB port, although the boot continues. > > I tried removing the supposed USB port from the services list without > success (success == not seeing the failed attempt to detect at boot) (MCC > / System / Services / stop and deselect usb / click okay) When I went back > in this morning to ensure that I had the process right to document here, I > found usb was back selected and running. I've again stopped it and > deselected it. > > this morning, the following appears in my syslog (login to root worked okay > this time): > > Jul 30 05:51:47 localhost kernel: usb.c: registered new driver usbdevfs > Jul 30 05:51:47 localhost kernel: usb.c: registered new driver hub > Jul 30 05:51:47 localhost kernel: usb-uhci.c: $Revision: 1.251 $ time > 23:13:16 Apr 15 2001 > Jul 30 05:51:47 localhost kernel: usb-uhci.c: High bandwidth mode enabled > Jul 30 05:51:47 localhost kernel: PCI: No IRQ known for interrupt pin D of > device 00:07.2. Please try using pci=biosirq. > Jul 30 05:51:47 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x6700, IRQ 0 > Jul 30 05:51:47 localhost kernel: usb-uhci.c: Detected 2 ports > Jul 30 05:51:47 localhost kernel: usb.c: new USB bus registered, assigned > bus number 1 > Jul 30 05:51:47 localhost kernel: usb-uhci.c: request_irq 0 failed! > Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver usbdevfs > Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! > Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver hub > Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! > Jul 30 05:51:47 localhost kernel: ip_tables: (c)2000 Netfilter core team > Jul 30 05:51:47 localhost kernel: ip_conntrack (768 buckets, 6144 max) > Jul 30 05:51:47 localhost kernel: usb.c: registered new driver usbdevfs > Jul 30 05:51:47 localhost kernel: usb.c: registered new driver hub > Jul 30 05:51:47 localhost kernel: usb-uhci.c: $Revision: 1.251 $ time > 23:13:16 Apr 15 2001 > Jul 30 05:51:47 localhost kernel: usb-uhci.c: High bandwidth mode enabled > Jul 30 05:51:47 localhost kernel: PCI: No IRQ known for interrupt pin D of > device 00:07.2. Please try using pci=biosirq. > Jul 30 05:51:47 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x6700, IRQ 0 > Jul 30 05:51:47 localhost kernel: usb-uhci.c: Detected 2 ports > Jul 30 05:51:47 localhost kernel: usb.c: new USB bus registered, assigned > bus number 1 > Jul 30 05:51:47 localhost kernel: usb-uhci.c: request_irq 0 failed! > Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver usbdevfs > Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! > Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver hub > Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! > > > -- > "Microsoft is a cross between the Borg and the Ferengi. Unfortunately, > they use Borg to do their marketing and Ferengi to do their programming." > -- Simon Slavin in asr
Re: [newbie] login problem
On Saturday 28 July 2001 12:46, Frans Ketelaars wrote: > > [frans@localhost frans]$ cat /etc/modules.conf | grep 180 > alias char-major-180 usb-ohci > > so it seems to have something to do with USB. > > The "Can't locate module ..." means just that: modprobe cannot find > the module, it does not exist or it's in the wrong place. > > [frans@localhost frans]$ locate usb-ohci > /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz > > Note the kernel version in the path. > > cat /proc/devices says char-major-4 is associated with ttyS. > Maybe something with the keyboard? > > Sorry I have no solution just information. > > -Frans Interesting. I have no USB ports on the machine, or so I believe (see below) and the installation should have detected that. I get a fail at boot time as services are being started when attempting to detect the USB port, although the boot continues. I tried removing the supposed USB port from the services list without success (success == not seeing the failed attempt to detect at boot) (MCC / System / Services / stop and deselect usb / click okay) When I went back in this morning to ensure that I had the process right to document here, I found usb was back selected and running. I've again stopped it and deselected it. this morning, the following appears in my syslog (login to root worked okay this time): Jul 30 05:51:47 localhost kernel: usb.c: registered new driver usbdevfs Jul 30 05:51:47 localhost kernel: usb.c: registered new driver hub Jul 30 05:51:47 localhost kernel: usb-uhci.c: $Revision: 1.251 $ time 23:13:16 Apr 15 2001 Jul 30 05:51:47 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jul 30 05:51:47 localhost kernel: PCI: No IRQ known for interrupt pin D of device 00:07.2. Please try using pci=biosirq. Jul 30 05:51:47 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x6700, IRQ 0 Jul 30 05:51:47 localhost kernel: usb-uhci.c: Detected 2 ports Jul 30 05:51:47 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jul 30 05:51:47 localhost kernel: usb-uhci.c: request_irq 0 failed! Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver usbdevfs Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver hub Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! Jul 30 05:51:47 localhost kernel: ip_tables: (c)2000 Netfilter core team Jul 30 05:51:47 localhost kernel: ip_conntrack (768 buckets, 6144 max) Jul 30 05:51:47 localhost kernel: usb.c: registered new driver usbdevfs Jul 30 05:51:47 localhost kernel: usb.c: registered new driver hub Jul 30 05:51:47 localhost kernel: usb-uhci.c: $Revision: 1.251 $ time 23:13:16 Apr 15 2001 Jul 30 05:51:47 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jul 30 05:51:47 localhost kernel: PCI: No IRQ known for interrupt pin D of device 00:07.2. Please try using pci=biosirq. Jul 30 05:51:47 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x6700, IRQ 0 Jul 30 05:51:47 localhost kernel: usb-uhci.c: Detected 2 ports Jul 30 05:51:47 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jul 30 05:51:47 localhost kernel: usb-uhci.c: request_irq 0 failed! Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver usbdevfs Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! Jul 30 05:51:47 localhost kernel: usb.c: deregistering driver hub Jul 30 05:51:47 localhost kernel: usb.c: null device being purged!!! -- "Microsoft is a cross between the Borg and the Ferengi. Unfortunately, they use Borg to do their marketing and Ferengi to do their programming." -- Simon Slavin in asr
Re: [newbie] login problem
root wrote: > > On Friday 27 July 2001 08:47, etharp wrote: > > well, we can look at the logs, if you want, or we could create a new user > > from the text prompt, and see how it logs in. > > per this suggestion, I pulled /var/log/syslog and compared a failed login to > a good one, and see one difference. Below are the last few lines from a > failed login. I have more if we need them: > > Jul 28 06:55:34 localhost modprobe: modprobe: Can't locate module char-major-4 > Jul 28 06:55:38 localhost last message repeated 35 times > Jul 28 06:55:38 localhost modprobe: modprobe: Can't locate module > char-major-180 [...] [frans@localhost frans]$ cat /etc/modules.conf | grep 180 alias char-major-180 usb-ohci so it seems to have something to do with USB. The "Can't locate module ..." means just that: modprobe cannot find the module, it does not exist or it's in the wrong place. [frans@localhost frans]$ locate usb-ohci /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz Note the kernel version in the path. cat /proc/devices says char-major-4 is associated with ttyS. Maybe something with the keyboard? Sorry I have no solution just information. -Frans
Re: [newbie] login problem
On Saturday 28 July 2001 08:40, etharp wrote: > have you ever tried to compile a kernel? on this machine? did you have this > problem before that? > nope. I reformatted my linux partititions and installed 8.0 clean, avoiding expert mode because I'm not an expert. -- "Gentlemen, it's in beta. That means it's like Windows. They're letting you test it while they continue to screw it up until it's totally useless." (Bigg Fredd in RCC talking about Google's temporary interface to the deja archives)
Re: [newbie] login problem
have you ever tried to compile a kernel? on this machine? did you have this problem before that? On Saturday 28 July 2001 09:36, root wrote: > On Friday 27 July 2001 08:47, etharp wrote: > > well, we can look at the logs, if you want, or we could create a new user > > from the text prompt, and see how it logs in. > > per this suggestion, I pulled /var/log/syslog and compared a failed login > to a good one, and see one difference. Below are the last few lines from a > failed login. I have more if we need them: > > Jul 28 06:55:34 localhost modprobe: modprobe: Can't locate module > char-major-4 Jul 28 06:55:38 localhost last message repeated 35 times > Jul 28 06:55:38 localhost modprobe: modprobe: Can't locate module > char-major-180 > Jul 28 06:55:40 localhost last message repeated 24 times > Jul 28 06:56:47 localhost modprobe: modprobe: Can't locate module > binfmt- Jul 28 06:57:03 localhost last message repeated 3 times > > > On a successful login, "localhost modprobe: modprobe: Can't locate module > binfmt-" is repeated only two times, then I get the same messge for a > collection of sound-* modules. The "can't find char-major-*" message > repeat the same number of times regardless of whether the login works or > doesn't. Meanwhile, I am successful in logging in via console mode if I do > a 'restart in console mode'. > > Incidentally, the failed login has gone from the previous exception to the > rule, to where I have to make multiple attempts, including powering down, > to get signed in. > > I did reinstall my printer last night, and fixed my halt problem per > someone else's documentation here. I assume the "now it is safe to turn > off your computer" is a windoze specific message, since I never see that. > I get to a message saying that the system is stopped after what seem to be > all the shutdown messages complete ok. > > > On Friday 27 July 2001 09:05, root wrote: > > > On Friday 27 July 2001 04:43, etharp wrote: > > > > is this while you wait to login? have you installed mandrake security > > > > and what level? (paranoid?) or a firewall? what reaction are you > > > > expecting? > > > > > > i was expecting no reaction, since I had never heard of that method of > > > logging on before. I hit alt-f4 at the point where otherwise I would > > > enter root and my password and hit go. > > > > > > The original problem when attempting to login via the normal login > > > panel, I sometimes was bounced back to the login panel without getting > > > logged in, and when that happened had to reboot before being successful > > > at logging in. > > > > > > When installing, I took the defaults for security and the firewall. > > > Before altering those, I'll want an explanation of why the bounce > > > occurs only some of the time instead of every time. It seems to me if > > > it was a security or firewall problem, the bounce would be consistent > > > instead of sporadic. > > > > > > > On Friday 27 July 2001 00:48, root wrote: > > > > > On Thursday 26 July 2001 16:34, etharp wrote: > > > > > > what happens if you hit ctrl+alt+f4 (or any other f-key up to f6) > > > > > > and log in? > > > > > > > > > > nothing. no reaction at all > > > > > > -- > > > "Gentlemen, it's in beta. That means it's like Windows. They're > > > letting you test it while they continue to screw it up until it's > > > totally useless." (Bigg Fredd in RCC talking about Google's temporary > > > interface to the deja archives)
Re: [newbie] login problem
On Friday 27 July 2001 08:47, etharp wrote: > well, we can look at the logs, if you want, or we could create a new user > from the text prompt, and see how it logs in. per this suggestion, I pulled /var/log/syslog and compared a failed login to a good one, and see one difference. Below are the last few lines from a failed login. I have more if we need them: Jul 28 06:55:34 localhost modprobe: modprobe: Can't locate module char-major-4 Jul 28 06:55:38 localhost last message repeated 35 times Jul 28 06:55:38 localhost modprobe: modprobe: Can't locate module char-major-180 Jul 28 06:55:40 localhost last message repeated 24 times Jul 28 06:56:47 localhost modprobe: modprobe: Can't locate module binfmt- Jul 28 06:57:03 localhost last message repeated 3 times On a successful login, "localhost modprobe: modprobe: Can't locate module binfmt-" is repeated only two times, then I get the same messge for a collection of sound-* modules. The "can't find char-major-*" message repeat the same number of times regardless of whether the login works or doesn't. Meanwhile, I am successful in logging in via console mode if I do a 'restart in console mode'. Incidentally, the failed login has gone from the previous exception to the rule, to where I have to make multiple attempts, including powering down, to get signed in. I did reinstall my printer last night, and fixed my halt problem per someone else's documentation here. I assume the "now it is safe to turn off your computer" is a windoze specific message, since I never see that. I get to a message saying that the system is stopped after what seem to be all the shutdown messages complete ok. > > On Friday 27 July 2001 09:05, root wrote: > > On Friday 27 July 2001 04:43, etharp wrote: > > > is this while you wait to login? have you installed mandrake security > > > and what level? (paranoid?) or a firewall? what reaction are you > > > expecting? > > > > i was expecting no reaction, since I had never heard of that method of > > logging on before. I hit alt-f4 at the point where otherwise I would > > enter root and my password and hit go. > > > > The original problem when attempting to login via the normal login panel, > > I sometimes was bounced back to the login panel without getting logged > > in, and when that happened had to reboot before being successful at > > logging in. > > > > When installing, I took the defaults for security and the firewall. > > Before altering those, I'll want an explanation of why the bounce occurs > > only some of the time instead of every time. It seems to me if it was a > > security or firewall problem, the bounce would be consistent instead of > > sporadic. > > > > > On Friday 27 July 2001 00:48, root wrote: > > > > On Thursday 26 July 2001 16:34, etharp wrote: > > > > > what happens if you hit ctrl+alt+f4 (or any other f-key up to f6) > > > > > and log in? > > > > > > > > nothing. no reaction at all > > > > -- > > "Gentlemen, it's in beta. That means it's like Windows. They're letting > > you test it while they continue to screw it up until it's totally > > useless." (Bigg Fredd in RCC talking about Google's temporary interface > > to the deja archives) -- -- "Gentlemen, it's in beta. That means it's like Windows. They're letting you test it while they continue to screw it up until it's totally useless." (Bigg Fredd in RCC talking about Google's temporary interface to the deja archives)
Re: [newbie] login problem
well, we can look at the logs, if you want, or we could create a new user from the text prompt, and see how it logs in. On Friday 27 July 2001 09:05, root wrote: > On Friday 27 July 2001 04:43, etharp wrote: > > is this while you wait to login? have you installed mandrake security and > > what level? (paranoid?) or a firewall? what reaction are you expecting? > > i was expecting no reaction, since I had never heard of that method of > logging on before. I hit alt-f4 at the point where otherwise I would enter > root and my password and hit go. > > The original problem when attempting to login via the normal login panel, I > sometimes was bounced back to the login panel without getting logged in, > and when that happened had to reboot before being successful at logging in. > > When installing, I took the defaults for security and the firewall. Before > altering those, I'll want an explanation of why the bounce occurs only some > of the time instead of every time. It seems to me if it was a security or > firewall problem, the bounce would be consistent instead of sporadic. > > > On Friday 27 July 2001 00:48, root wrote: > > > On Thursday 26 July 2001 16:34, etharp wrote: > > > > what happens if you hit ctrl+alt+f4 (or any other f-key up to f6) and > > > > log in? > > > > > > nothing. no reaction at all > > -- > "Gentlemen, it's in beta. That means it's like Windows. They're letting > you test it while they continue to screw it up until it's totally useless." > (Bigg Fredd in RCC talking about Google's temporary interface to the deja > archives)
Re: [newbie] login problem
On Friday 27 July 2001 04:43, etharp wrote: > is this while you wait to login? have you installed mandrake security and > what level? (paranoid?) or a firewall? what reaction are you expecting? i was expecting no reaction, since I had never heard of that method of logging on before. I hit alt-f4 at the point where otherwise I would enter root and my password and hit go. The original problem when attempting to login via the normal login panel, I sometimes was bounced back to the login panel without getting logged in, and when that happened had to reboot before being successful at logging in. When installing, I took the defaults for security and the firewall. Before altering those, I'll want an explanation of why the bounce occurs only some of the time instead of every time. It seems to me if it was a security or firewall problem, the bounce would be consistent instead of sporadic. > > On Friday 27 July 2001 00:48, root wrote: > > On Thursday 26 July 2001 16:34, etharp wrote: > > > what happens if you hit ctrl+alt+f4 (or any other f-key up to f6) and > > > log in? > > > > nothing. no reaction at all > > -- "Gentlemen, it's in beta. That means it's like Windows. They're letting you test it while they continue to screw it up until it's totally useless." (Bigg Fredd in RCC talking about Google's temporary interface to the deja archives)
Re: [newbie] login problem
On Thursday 26 July 2001 16:34, etharp wrote: > what happens if you hit ctrl+alt+f4 (or any other f-key up to f6) and log > in? > nothing. no reaction at all > On Thursday 26 July 2001 16:30, root wrote: > > running mandrake 8.0 > > > > on occasions following what is currently an undectable pattern, I get to > > the login window where i would enter root or my user name and password, > > enter the uid and password correctly, the system thinks for awhile and > > bounces me back to the same login window. > > > > I have to reboot under those circumstances, sometimes several times, > > sometimes powering off entirely and waiting for bios to clear, before the > > system accepts my uid and password. > > > > I'm careful to comfirm that I have entered the password correctly, and > > caps lock is off. The password is simple enough that mistyping multiple > > times is not a likely explanation. > > > > I've never had a situation where one (root or user) accepts but the other > > doesn't. > > > > login is set to start kde. I do not get to the kde loading panel before > > the bounce occurs. > > > > ideas? > > > > -- > > "Gentlemen, it's in beta. That means it's like Windows. They're letting > > you test it while they continue to screw it up until it's totally > > useless." (Bigg Fredd in RCC talking about Google's temporary interface > > to the deja archives) -- -- "Gentlemen, it's in beta. That means it's like Windows. They're letting you test it while they continue to screw it up until it's totally useless." (Bigg Fredd in RCC talking about Google's temporary interface to the deja archives)
Re: [newbie] login problem
what happens if you hit ctrl+alt+f4 (or any other f-key up to f6) and log in? On Thursday 26 July 2001 16:30, root wrote: > running mandrake 8.0 > > on occasions following what is currently an undectable pattern, I get to > the login window where i would enter root or my user name and password, > enter the uid and password correctly, the system thinks for awhile and > bounces me back to the same login window. > > I have to reboot under those circumstances, sometimes several times, > sometimes powering off entirely and waiting for bios to clear, before the > system accepts my uid and password. > > I'm careful to comfirm that I have entered the password correctly, and caps > lock is off. The password is simple enough that mistyping multiple times > is not a likely explanation. > > I've never had a situation where one (root or user) accepts but the other > doesn't. > > login is set to start kde. I do not get to the kde loading panel before > the bounce occurs. > > ideas? > > -- > "Gentlemen, it's in beta. That means it's like Windows. They're letting > you test it while they continue to screw it up until it's totally useless." > (Bigg Fredd in RCC talking about Google's temporary interface to the deja > archives)
[newbie] login problem
running mandrake 8.0 on occasions following what is currently an undectable pattern, I get to the login window where i would enter root or my user name and password, enter the uid and password correctly, the system thinks for awhile and bounces me back to the same login window. I have to reboot under those circumstances, sometimes several times, sometimes powering off entirely and waiting for bios to clear, before the system accepts my uid and password. I'm careful to comfirm that I have entered the password correctly, and caps lock is off. The password is simple enough that mistyping multiple times is not a likely explanation. I've never had a situation where one (root or user) accepts but the other doesn't. login is set to start kde. I do not get to the kde loading panel before the bounce occurs. ideas? -- "Gentlemen, it's in beta. That means it's like Windows. They're letting you test it while they continue to screw it up until it's totally useless." (Bigg Fredd in RCC talking about Google's temporary interface to the deja archives)
[newbie] Login problem...
Hello, When I reboot my system running 7.2 just before the graphical login appears I get a message that says something like "user does not exist!" then the graphical login appears as usual. Does anyone know why this would happen? Thank You, Vincent A. Primavera
[newbie] login problem
Hello, I cannot login anymore. I just upgraded a few packages. In particular I upgraded initscripts to something like 5.27-20mdk. and a few others that shouldn't effect anything (ie., rpm 3.0.5 rpm-devel, rpm-python). When I rebooted I found that after typing my name and password I was returned to the login prompt after being acknowledged as logging in. I entered the system through 'I' interactive bootup and couldn't find any problems. I created a new user but to the same effect. The log records PAM_pwd[556]:(login) session opened for user my_name by LOGIN (uid=0) immediately followed by PAM_pwdb[556]:(login) session closed for user my_name I receive essentially the same result through gui logins. I received a comment that it has something to do with /etc/profile.d My system is Mandrake 7.1 on a Shuttle MVP3 motherboard, 196megs ram The packages I have installed recently include initscripts 5.27-20-mdk fileutils-4.0-13mdk rusers-0.17-2mdk procps-2.0.7-6mdk man-pages-1.31-1mdk ipchains-1.3.9-8mdk cpio-2.4.2-18mdk dev86-0.15.0-3mdk devfsd-1.3.10-3mdk firestarter-0.4.1-1mdk running firestarter after install caused a core dump. Any help would be very much appreciated. Thanks, Timothy please reply to [EMAIL PROTECTED]
Re: [newbie] Login problem
Um, You probably dont want to hear this but its all I can suggest what I'd do. Perhaps reinstall fresh - selecting format new linux partitions as you go (when it asks during the install). Select just the basic packages for a first install, just to get it up and running. Then go back and install other stuff once you've got it working ok where you can boot and at least get in :) regards Gina - Original Message - From: "Alan Shoemaker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, 13 February 2000 06:07: am Subject: Re: [newbie] Login problem > CyberI'm sorry you're not getting any response to your > problem. I'm sure it's not because people are ingoring you for > some reason, but instead because, like me, they haven't > experienced a problem like yours and therefore haven't anything > helpful to contribute. Perhaps if you expanded your description > a bit to include more about your hardware and more about the > choices you made during the installation process. Sorry I can't > be of more help. > > Alan > > > > CyberNEMESIS wrote: > > > > Dear All, > > i still have this silly problem > > i install Mandrake 6.1, the installation went so smooth, the > > system rebooted and i got the login promt. > > but when i try to log as root or any other user i can't > > the login screen freezes and i don't even get the passward > > promt. > > can some one help me with that, it's the third time i post > > this problem. > > > > c.n.
Re: [newbie] Login problem
CyberI'm sorry you're not getting any response to your problem. I'm sure it's not because people are ingoring you for some reason, but instead because, like me, they haven't experienced a problem like yours and therefore haven't anything helpful to contribute. Perhaps if you expanded your description a bit to include more about your hardware and more about the choices you made during the installation process. Sorry I can't be of more help. Alan > CyberNEMESIS wrote: > > Dear All, > i still have this silly problem > i install Mandrake 6.1, the installation went so smooth, the > system rebooted and i got the login promt. > but when i try to log as root or any other user i can't > the login screen freezes and i don't even get the passward > promt. > can some one help me with that, it's the third time i post > this problem. > > c.n.
[newbie] login problem
Dear all, i've installed Mandrake 6.1 and i can't login at all. i just get the localhost@login promt. and whenever i write root and press Enter the root word disappears and nothing happens at all, and the promt still the same. can any one help me with that ... pls TIA cn
Re: [newbie] login problem
If you are using Mandrake 6.0, or 6.1, you should me able to set this up using Xconfigurator (Ithink that's the one). At the end of the setup process, you should be offered a choice to start X automatically. If you answer "yes", this should do it. The other way is to edit the /etc/initab file. Change the line with: ID:3:initdefault: to: ID:5:initdefault: using your favorite text editor My choice is pico, since it is simple to use, and the commands you will need to save the file, and exit the editor are displayed at the bottom of the screen. Ernie On Mon, 25 Oct 1999,Don Whitman wrote: | I just did an update for the first time. Now when I start linux it takes me to | the penguin login screen instead of the kdesktop login screen. I can still | startx from there but I would like to know how to change back to the way it | was. I looked in linuxconf but could not find anything. Thanks D. | | | Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
Re: [newbie] login problem
On Mon, 25 Oct 1999, you wrote: > I just did an update for the first time. Now when I start linux it takes me to > the penguin login screen instead of the kdesktop login screen. I can still > startx from there but I would like to know how to change back to the way it > was. I looked in linuxconf but could not find anything. Thanks D. > As root, edit your /etc/inittab so that it goes from id:3:initdefault: to id:5:initdefault: This will put you back to an X-based login screen. John
