i have to reinstall my pc with a testing version. The installation almost is the same as stable version (lenny). But, the problem is that, i can't login it after the installation completed. The new user i created during installation is invalid! So, i have to enter the single user mode, to my surprise, the new user(i created before) doesn't exist! So, i add a user here.But, i still can't login to my system as the normal mode.How should i resolve such a problem?
I've been installing proftpd on a server running fedora 8. It is setup in standalone server type, and I checked that the process is running and listening to port 21. When I try to login using a ftp client in Normal mode with root user & password , I receive first a 220, then a 530 login incorrect error. Can you help me?
I've been pasting my proftpd.conf configuration file below
how do I make grub boot to allow me to choose, like safe mode and normal mode and all that second, how do I do automated back ups (preferably using file copy) for something like every sunday at 11:00 am using the command line, i use to know but forgot.
I played with the graphics in kde4 and seem to have losy my installation. i have tried the rescue system option, recover system options and in desperation (i was just about to reinstall) tried booting in failsafe mode, and it worked!
where do i go to find out what the problem is regarding the normal boot mode? i think my pc is starting to resent the continual use of the reset button!
I accidentally chose the "recovery mode" and now i dont know what to do. What commands i have to enter to go back to normal ubuntu mode with graphic etc?
I've installed the latest testing version, which has 2.6.32 kernel perfect for me. I was very amazed when check system monitor and saw it runs with 90MB RAM, meanwhile my ubuntu desktop takes only 400, and the pocket version of ubuntu on vmware has 180MB RAM.
The questions is: Debian runs on vmware 7. Could the amount of RAM change when switching to a normal environment? Or I have to test and see what is happening..What problems could occur when using a testing version?
I don't what happened but yesterday I was working normally and then I shutdown the computer, today when I opened ubuntu it took me to tyy1 login screen, I entered my username and password then it took me to the normal login screen with the login drums sound and it wrote on my account (logged in) so I clicked it and I entered my password again and then I got to my ubuntu so what went wrong and how to fix it also I noticed that a new terminal in system tools occurred called Kernel (I didn't add it)
I'm using ubuntu 10.10 on Dell inspiron 1520 with Nvidia 8600GT and 3GB RAM
Important: this happened after update to generic-headers-24
I just completed a fresh install of the weekly jessie build (downloaded today). All I've done is install updates, add my username to sudoer list, and reboot. When I did, the xfce panel was not there. When I right clicked, Apps, Panel, it opened with an error that I cannot make changes unless I save my session and that it's in kiosk mode. After a logoff or reboot, it's still not there. I saw one thread asked for the output of /.xsession-errors, which I've done, and it doesn't look good... I'm just not sure how to fix:
Code: Select allopenConnection: connect: No such file or directory cannot connect to brltty at :0 /usr/bin/x-session-manager: X server already running on display :0 xfce4-session-Message: ssh-agent is already running; starting gpg-agent without ssh support
Just a little disappointed. I downloaded the 11.4 Gnome by about midnight, checked the CD for integrity,and started the Live CD, and it worked quite well. Installed it, but troubles started. OpenSuse 11.4 won't boot up in the normal mode, but would boot up in the safe mode only. I am now writing from the safe mode, but would like to boot up normally. It get stuck after the first verbose page. And not a move from there. The laptop is Lenovo T400, Core2Duo with 4GB RAM, screen 1440x900. No problem with any other distros up to now.
I've installed UNR 10.04 on an old UMPC. Graphics are a total mess, even console text doesn't display properly. All I get is a bunch of pixels, smeared across the screen. I'd blame KMS, but that's only supposed to affect X. Anyway, according to https://wiki.ubuntu.com/X/KernelModeSetting/, "KMS is enabled by default for the -intel, -ati, and -nouveau drivers. It is not available for any other drivers". Mine isn't any of those, so KMS shouldn't be enabled at all. I've found that failsafeX in a recovery console works OK. My question is, how can I get UNR 10.4 to default to failsafeX in normal mode?
I'm posting this in the "General Help" category, because it doesn't really fit in another one. Feel free to move this thread, if it's the wrong place. I'm having a problem with my Linux. Since today, my Kubuntu 10.10 (running on an Dell XPS M1530) doesn't but anymore. Neither normal, nor recovery-mode is working. I also tried out different kernels in the grub-menu without any success. The boot-process stops at:
Code:
... ... [2.115441] EXT4-fs (sda2): mounted filesystem with ordered data mode: Opts: (null) Begin: Running /scripts/local-bottom ... done. done.
Shut down the machine yesterday, got an error booting today. Since I'm new to Ubuntu (been using it for about a month now), I don't know what logs to check, what utilities to run, where to find bootup error message so I can copy here. I am now using it in recovery/low-graphics mode.
I've installed fglrx drivers with 1click install on openSuse11.3. If I try to boot in "normal mode" I end up in black screen. However if I boot in safe mode, then login and startx, everything works ok
Code: ~> fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI Mobility Radeon HD 4300 Series OpenGL version string: 3.3.10151 Compatibility Profile Context Shows fglrx works OK, as well as overall performance is pretty good.
I've done Code: aticonfig --initial radeon drivers is also blacklisted but running (if it means something) Code: # depmod -a; lsmod | grep radeon radeon 868858 0 ttm 64561 1 radeon drm_kms_helper 32944 1 radeon drm 221516 3 radeon,ttm,drm_kms_helper i2c_algo_bit 6728 1 radeon
When I boot into recovery mode I get fsck from util-linux-ng 2.16 /dev/sda1: clean, 148044/217728 files, 630631/869510 blocks.And then it stops. Booting into normal mode results in an endless hang. I'm not sure what the error means, or how to fix it.I'm running Ubuntu Netbook Remix on a Dell Mini 9.
I get a blank screen with no progress when I use normal mode, but I am able to get into desktop environment using recovery mode and selecting safe graphics mode from there. Anything I could to do to restore my normal desktop environment.
I tried to make Compiz work using the experimental 3D support of the free Nvidia driver, because I am suffering from a bug in the proprietary driver (click here for launchpad entry). The free driver I mean is the one that shows up as "Experimental 3D support for NVIDIA cards" in the "Additional Drivers" manager (note: for some reason, this option will only present itself when no proprietary driver is currently active).
Now the strange thing is: the driver does not provide 3d support, and behaves generally awful (lots of glitches and so on) when I boot my system normally. But when instead I boot from the grub menu into recovery mode, then select "failsafe graphics", and then select "restart X", the whole thing works perfectly! So now I am running the experimental 3d driver, I have compositing working, 3d animations on docky. Somehow, the failsafe boot sequence does something right that my normal boot sequence does not. When I reboot in normal mode, everything is screwed up again.
I have no idea what statistics about my system I should include here, because I really have no idea what could possibly be wrong. I am running 32bits Natty in Classic mode, on an Ahtlon Dual Core 4850e machine, with a GeForce 6150 LE graphics card. These are the normal and recovery entries in my grub.cfg:
Code:
menuentry 'Ubuntu, with Linux 2.6.38-8-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os { recordfail set gfxpayload=$linux_gfx_mode insmod part_msdos
My previously running debian system recently started failing with systemd failure messages as some services are being started. It never completes. I can log into recovery mode.
I added systemd.log_target=kmsg systemd.log_level=debug into my grub parameters.
After I do that all that I see scrolling down the page on boot are:
systemd-journald[36] /dev/kmsg buffer overrun, some messages lost and the occasional systemd[1] Looping too fast Throttling execution a little
Is there a way that I can boot without systemd using sysvinit?
It happened when I updated my php5.4 to 5.5 version on my small Debian 7 server. I am only getting GRUB right after BIOS boot pass, then none of the keys working even C or Shift buttons to go to command promt except CTRL+ALT+DEL.
I have tried rescue mode with live CD, selected myserver/root/ partition to install GRUB but not worked.
How to recover my server, I have some important data in it and I don`t want to destroy them.
I used to dual-boot, windows 7 and Ubuntu, but like a month ago, i decided to finally kill windows, so when i finished doing so, i had 160 GB. of free space. I never resized my ubuntu partition, since it had like 80 GB. of free space.Yesterday, I re-compiled my kernel, mainly to enable FrameBuffer in the console. So i decided it was time to resize my partition, to use the whole HDD.Turns out, that i had a little bit of problems compiling my kernel, and yes it took really a lot more than i thought ( I had to compile it twice ) but finally i got it working.
i still got some 100 GB. free, so is there anyway to get my system to it's normal weight?.I really don't wanna miss all my info, specially my programs, and customized desktop, it really took me a wile to set compiz just the way i like it.IM REALLY SORRY, I KNOW IT WAS MY FAULT, BUT I REALLY DON'T WANNA LOSE ALL THAT GB. NOR MY SYSTEM.
I attempted to install Catalyst 10.11 for my ATI HD 2600XT and the system now only displays lines and a large block of pixels where the mouse would go. CTRL-ALT-F1 kills the system and does not provide a command prompt. This is a single installation, not dual-boot, but there is no Press Esc to access the Grub menu during startup so I cannot choose safe mode. I attempted to get into Recovery mode using the flash drive that I used to install the system and it tells me there is no Recovery kernel (I used the 64-bit Desktop installer, not alternative). Does anyone know an alternative to get into the Grub menu other than ESC during bootup? Alternatively, do I need to download the 64-bit Alternative ISO and create a new boot disk with it so I can access Recovery mode? Is there something else I'm not thinking of?
I was under the impression the Linux (in my case the Fedora OS) is very secure. However I've learnt with deep concern that that one can have access to the system during system startup i.e one can give various startup directives and bypass the normal login UI to have direct root access.
Is there a way to disble this so that the directives during startup are fixed and cannot be altered. I would like to make the system secure to the maximum extent possible.
From time to time system freezes with no particular motive but most often when watching you tube video in full screen mode. How to diagnose freeze, hang, blocking problems in debian jessie system amd 64 gnome 3?
I am having a funky issue at login. When I enter my username/password at login with the GUI (I disabled the list of users some time ago) the screen will flicker then return me to the login screen. There is no notification of an error. It doesn't matter if I try the recovery console or safe mode there is the same issue when I try and login with this user. However, I can login with a different user open a console and su to that user that wouldn't login at the GUI.
Seems that I have been having a problem with the initial user login on Ubuntu 10.10 Netbook. Whenever I try and login the normal way (from standard gui login) my system comes to a standstill and I have to switch to command line (ctrl+alt+F2) and restart/shutdown my computer in that fashion. The only way that I can login and actually see my desktop without any hint of my system freezing up is by booting into the ubuntu recovery Console using the dpkg function to remove any broken packages, select boot normally (where I have to login through the command line), and manually startx.
Originally I was running an x64 version of ubuntu desktop 10.10 but I switched to an x86 version of netbook due to many incompatibilities in software and trouble finding x64 software for my system. When I was on Ubuntu Desktop I had a similar problem where it would freeze at login as well but I fixed it by removing compiz & compiz-core. I tried that with this version of the OS but had no luck because it said that compiz was not installed.
Not a major issue, just somewhat annoying that I have to resort to other means to login
PS: My computer is a Toshiba P500-026. Some stats are listed below in my signature if its relevant to my problem.
Is it possible to have multiple passwords on the same account, where one password allows only normal login and another only when accessing the machine remotely (for example, via ssh)?
I am unable to login as normal user. I am sure that my password is correct. What are the possible reasons behind this and also the solutions. My /etc/password and /etc/shadow files are good and my login haven't set to /etc/nologin.
Actually this a question asked to me by a Novell(Suse Enterprise Linux) Regional manager.
