Re: OT Password problem -
On 2015-07-10 12:42, Joe Zeff wrote: On 07/10/2015 07:33 AM, Matthew Woehlke wrote: probably have a more benign reason (maybe to stop people that don't know what they're doing from accidentally bricking their machines). That's no excuse. Once you've paid for the machine and received it, what you do with it is none of their business. ...so if I sell you a gun, I should be sure to ship it to you with the safety *off*? Sure, that might be more convenient, but OTOH it's not like I welded the safety in the on position. I agree with the sentiment, and that's why I take a very low view of dealers that password lock the BIOS *and won't tell you the password*. If they're happy to tell you... I still don't necessarily agree with having one in the first place, but I'm much less inclined to ascribe sinister motives. (Or, as Bob indicated, maybe it was an accident. Maybe they test the BIOS password lock of every computer they sell and sometimes forget to remove the password again.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: OT Password problem -
On 2015-07-09 16:52, Bob Goodwin - Zuni, Virginia, USA wrote: On 09/07/15 13:16, Matthew Woehlke wrote: With no previous experience? Probably not. Now? I'd... be very cautious about buying a refurbished computer. Especially from someone that deals in used computers. You're probably better off buying from an honest individual making a one-time sale, actually. (The problem there of course is knowing whether or not the individual*is* honest.) My experience has been different. I bought a motherboard from Craig's list from a local, It worked for a couple of weeks and died, refused to complete the POST. He didn't want to hear about it, it was as is I guess. Computers I've bought on-line from dealers specializing in used equipment have always worked and held up long enough for me to want to replace them with something newer. They have even settled problems with a phone call. I do admit I have very limited experience, and that not first-hand :-). Personally I always buy new when I can, at least for things like computer equipment. (And cars. If I *could*, I'd prefer new houses, too, though at least there you do inspections when you buy used. Things like books, furniture, etc. where visible condition is usually a good indicator as to the actual condition, are another matter though.) Today's problem is solved. I e-mailed them this morning and they responded this afternoon. The dealer support guy [ZoomUsa] requested the system number, I provided it, and he immediately returned the password required with the necessary instructions. That's good to hear; it means this dealer isn't locking the BIOS because they are trying to hide something or wring more money out of you, and probably have a more benign reason (maybe to stop people that don't know what they're doing from accidentally bricking their machines). Anyway, glad they were able to help you. Good luck with your new Fedora system! :-) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: telnet session closing with ^]
On 2015-07-10 09:26, Maurizio Marini wrote: Very often I check smtp server for any issue using telnet mailserver 25 pop3 server, too, to check credentials, when a customer complain: server says my credentials are wrong I telnet pop3 server on port 100 and I realize he is using wrong credentials and many other amenities for sure I don't use telnet instead of ssh, of course :) *But*, as Gordon pointed out, those *aren't* telnet servers, and you'd probably do better to use 'nc' than 'telnet'. While 'nc' isn't exactly feature-filled, you're not able to *use* any telnet features with things that aren't telnet servers anyway, so you really aren't losing anything. (Admittedly, I've done the same thing... it's habit, and habits die hard. This is one worth breaking, though; 'nc' should exit with a ^D, which Konsole won't eat. Or had better not, because that would be a serious bug if it did.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: OT Password problem -
On 2015-07-08 17:47, Bob Goodwin - Zuni, Virginia, USA wrote: I bought a used Dell Latitude E4310 that I want to replace Windows7 on with Fedora-22. Unfortunately the BIOS is locked and I do not have the admin password for it. A phone call to Dell was unproductive and none of the passwords offered in an on-line application work. Does anyone know what I can do to access this computer. I can return it, bought through Newegg, but it looks good so far, in new condition and the price is right. It even has a working battery. In my experience, *new* Dell machines do not have locked BIOS. However, I have a friend who recently bought a refurbished Dell machine that had been BIOS locked. It's most likely the entity that refurbished the machine that locked the BIOS. You'll need to contact them to obtain the password / do research on them (not Dell) to find typically used passwords. Personally I consider this practice abhorrent and would never buy such a machine or deal with sellers that engage in such practices. Also, FWIW, this friend has had terrible problems with his machine. (A locked BIOS is a red flag; the seller doesn't want you to have full control of the system. You'd better ask yourself *why?*. It may be to try to extort money out of you later for service, or it may be to hide a problem with the machine. Either one isn't good news for you.) My advice: don't buy used computers. Build your own from new parts, or buy new from a reputable dealer. With used, you never know what you're getting (e.g. did someone sell it because some hardware component is going bad?) and you can easily end up having to spend more money to fix it than if you'd bought new. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: OT Password problem -
On 2015-07-09 10:55, Bob Goodwin - Zuni, Virginia, USA wrote: On 09/07/15 10:04, Matthew Woehlke wrote: In my experience,*new* Dell machines do not have locked BIOS. However, I have a friend who recently bought a refurbished Dell machine that had been BIOS locked. It's most likely the entity that refurbished the machine that locked the BIOS. You'll need to contact them to obtain the password / do research on them (not Dell) to find typically used passwords. Personally I consider this practice abhorrent and would never buy such a machine or deal with sellers that engage in such practices. Also, FWIW, this friend has had terrible problems with his machine. (A locked BIOS is a red flag; the seller doesn't want you to have full control of the system. You'd better ask yourself *why?*. It may be to try to extort money out of you later for service, or it may be to hide a problem with the machine. Either one isn't good news for you.) My advice: don't buy used computers. Build your own from new parts, or buy new from a reputable dealer. With used, you never know what you're getting (e.g. did someone sell it because some hardware component is going bad?) and you can easily end up having to spend more money to fix it than if you'd bought new. First, I did not anticipate this problem when I ordered the device. Would you have expected that? With no previous experience? Probably not. Now? I'd... be very cautious about buying a refurbished computer. Especially from someone that deals in used computers. You're probably better off buying from an honest individual making a one-time sale, actually. (The problem there of course is knowing whether or not the individual *is* honest.) I bought a used ASUS netbook off eBay that has been a truly wonderful little machine. IIRC the seller stated it had been booted once but was otherwise brand new; presumably he just didn't want it for whatever reason. I put in a larger memory module and replaced the spinning drive with an SSD and have never had any issues with it. But anyway, that's general advise (i.e. for future reference / others thinking about buying used). I do hope you can get your issue resolved and don't have further trouble. If all else fails I can return it, however I believe it is worth the effort to get the problem corrected, at least give the seller a chance to respond, he is probably reputable, certainly I must assume so until proven otherwise. I would strongly recommend you try to install Fedora before your return period expires if at all possible. My friend was unable to install it, and had issues reinstalling Windows later. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: telnet session closing with ^]
On 2015-07-09 12:40, Maurizio Marini wrote: When I use telnet inside Konsole, to close telnet: Please tell me you're connecting to a *really* old and/or dumb device and not another at-least-semi-modern *nix machine. If not... just do yourself a HUGE favor and use SSH. (Seriously... even if you don't [think you] need the encryption, use ssh. For one, it's 'kill' sequence is enter,'~','.', which is very unlikely to ever be consumed by any terminal emulator.) once upon a time, pressing Contr and ] closed telnet session, now it enlarge fonts, sadly. KF5? You could try asking on Konsole's list and/or filing a bug. It seems to work on KDE4 (Fedora 20). I have searched into Konsole/Settings/Edit currente Profile.../Keyboard Kde Menu/Settings/System settings/Shortcuts and Gestures but I haven't found anything relevant Did you try Konsole/Settings/Configure Shortcuts? -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora download and application
On 2015-07-03 12:57, Nikkita Miles wrote: New to Fedora OS use. Have windows 7 currently on laptop Want to install Fedora Need suggestion on best Fedora product to use Need suggestion on how to begin Need complete step thru process Real new to conversion process If you don't already know what flavor of Fedora you want, I would *strongly* recommend that you download the live images of several (definitely the main gnome image and probably the KDE spin; maybe also the xfce and/or lxde spins too) and play with them for a while to get a feel for which you like best *before* you make any changes to your system. (That said... you *can* install a different desktop later, but you'll get best results installing the right one from the get-go. Also, focus on the desktop experience, not issues like what web browser or office suite is used for a particular spin, as it's very easy to install different ones later. Or, if you have lots of RAM, you can install additional software in the live session... you'll get a clean slate when you reboot, though, unless you set up a USB stick with a persistent overlay.) As far as the process, if you don't care about keeping your existing Windows install and dual-booting, the installer is pretty straight forward. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F22 unusable - system freezes on login
I recently installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seems to run okay, but when I try to boot the installed OS, it freezes when I try to log in. The machine is effectively unusable as a result. Through much pain and anguish I have managed to install updates (up to date as of earlier today), to no effect. This affects login regardless of the method: graphical, tty, ssh, running 'login' from an emergency shell. If I'm lucky, TTY switching still works, but any login attempt hangs, and some take the whole system out. Only booting in emergency/maintenance/single mode works. My /var/log/messages is corrupt and contains no useful information. /var/log/boot.log has nothing obvious. The only potential clue I've seen is in dmesg: snd_hda_intel :01:00.1: Enabling via VGA-switcheroo snd_hda_intel :01:00.1: CORB reset timeout#2, CORBRP = 65535 The internet has some suggestions¹ that this may be the problem. There are references to adding options snd-hda-intel enable=0,1,0 to a configuration file, but the file referenced does not exist. (¹ See https://bbs.archlinux.org/viewtopic.php?pid=1460933 for example.) Any ideas? Unfortunately it's near impossible to diagnose this because I can't have a usable shell while tickling the issue. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-23 21:22, Suvayu Ali wrote: On Tue, Jun 23, 2015 at 10:00:14AM -0400, Matthew Woehlke wrote: On 2015-06-22 14:15, Marko Vojinovic wrote: As a side note, AFAIK now sshd is disabled on fresh installs. Do a systemctl enable sshd and systemctl start sshd (and verify with systemctl status sshd), and retry to log in over the network. I doubt it will work, but it's worth a try. I did figure out the appropriate incantations to get the network to be active on boot (sshd - 'systemctl enable sshd' was comparatively easy). I'm seeing the same behavior with ssh login as with local; it appears to accept the password, but I never get a shell. (If it wasn't a brand spanking new install - and happening for root also - I would suspect something being run via .bashrc...) Did you try with -vvv? That could give you where it gets stuck. ... debug2: shell request accepted on channel 0 Last login: Thu Jul 2 14:52:56 2015 from 192.168.1.183 ...and it's stuck. AFAICT there's nothing wrong with ssh; it's spinning up a login session / shell that doesn't work. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-07-02 13:56, Chris Murphy wrote: On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke wrote: I recently installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seems to run okay, but when I try to boot the installed OS, it freezes when I try to log in. The machine is effectively unusable as a result. Is it actual frozen? The login *process chain* is frozen. On a good day (although I don't think this has been the case since the originally-installed kernel) I can switch to a different TTY and futilely try again. Or you just can't see anything on the display? The display is unchanged; I still see the login dialog / prompt / whatever was on screen previously. (Although with updated kernels, TTY switching results in an unrecoverable black screen.) Can you ssh into it? Ah... no? This affects login regardless of the method: graphical, tty, *SSH* [...] (emphasis added) That is, ssh connects, but the login never completes and I never get to a shell. I get Last login: [...], and then nothing; it's stuck at that point. (And if I kill ssh and try again, I can still connect, so indeed, the kernel is still alive.) (In my various attempts to make things better in emergency mode - the only way I've been able to get a usable shell - I was able to enable sshd and coax the network into coming up on boot.) Try booting with boot parameter nomodeset. Does that change anything? Hmm... Yes. Seems to work okay with nomodeset. But why does that break *ssh*? (And where - that is, against what - do I file a bug report?) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange booting problem
On 2015-06-30 19:01, jd1008 wrote: So, how can I proceed with a brand new drive, dd /dev/zero into the first ... say 4K bytes, partition it with fdisk, do not mark any partition bootable, so that bios will skip over it ? Don't know why no one's mentioned this, but... you could always just install an actual bootloader on the drive that boots from the device from which you really want to boot. (I think you can do this with grub...) Of course, plugging that drive into any other computer might make for an interesting experience :-). -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-22 14:15, Marko Vojinovic wrote:
If the same set of steps don't work and then start working and then
don't work again, I am thinking memory or the harddrive.
Hmm... and... first try (just now) to boot the LiveCD got stuck ('LSB
init' IIRC). Second worked...
Boot from a live image, do a memcheck
How do I do that? (Last I recall this was a tool one had to boot into,
but I don't see an option for that?)
FWIW The Dell OBD extended memory check passed.
and do a fsck on all partitions.
I get an updating bad block inode on every single partition...? But
otherwise nothing, despite doing a thorough non-destructive write scan.
(Is this indicative of a real problem? Or just because I can never do a
clean shutdown?)
Does the machine work reliably under the live image?
See above. Otherwise, seems okay, though I've not done much.
Also, just for completeness, what is your video hardware?
ATI/AMD Saturn XT [FirePro M6100]
Another stab in the dark is CPU temperature --- is the machine maybe
overheating? Does the cpu fan work? Does it sound normal? Are any parts
of the machine unusually hot to touch?
Fan and exterior temp seem okay. HW sensors report the CPU cores around
54°-59° (C), which is slightly lower than my other laptop.
As a side note, AFAIK now sshd is disabled on fresh installs. Do a
systemctl enable sshd and systemctl start sshd (and verify with
systemctl status sshd), and retry to log in over the network. I doubt
it will work, but it's worth a try.
I did figure out the appropriate incantations to get the network to be
active on boot (sshd - 'systemctl enable sshd' was comparatively easy).
I'm seeing the same behavior with ssh login as with local; it appears to
accept the password, but I never get a shell. (If it wasn't a brand
spanking new install - and happening for root also - I would suspect
something being run via .bashrc...)
--
Matthew
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-20 06:38, Tim wrote: Allegedly, on or about 19 June 2015, Matthew Woehlke sent: Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh, *not at all*. No login -- never even tries to start X (not as my user, anyway). (Hrm... on that note, it's interesting to note that the one and only GUI program I was able to try to run is Konsole... I have to ask: If you were unable to login, how were you able to run anything (such as Konsole)? *Once and only once* I was able to get a desktop session, which allowed me to *try*, unsuccessfully, to run Konsole. (IIRC this was on the second attempt; the first had already failed in the manner that I'm now seeing always, and I was intending to run updates.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 20:27, Suvayu Ali wrote: On Fri, Jun 19, 2015 at 05:47:49PM -0400, Matthew Woehlke wrote: On 2015-06-19 17:27, Suvayu Ali wrote: In emergency mode, could you look at what logind was up to in the previous boot? Something like the following should work: # journalctl -b -1 -u systemd-logind You could compare with the current boot by switching the -1 to 0. Maybe this will give you clues. 16:47:38 New session c1 of user sddm. 16:47:56 New session 1 of user matthew. 16:48:24 Power key pressed. 16:48:24 Powering Off... 16:48:24 System is powering down. Nope, nothing interesting. Okay that tells me the login actually worked from the perspective of logind, but something else prevented the next step. [...] you could try booting with enforcing=0 among your kernel arguments and see if you can login. And of course checking permissions is easy from emergency mode. Actually, I tried that already... no joy. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 15:10, Joe Zeff wrote: On 06/19/2015 11:26 AM, Matthew Woehlke wrote: On 2015-06-18 17:47, Joe Zeff wrote: There should also be a ~/.xsession-errors.old and with luck, it might have something in it. There isn't. (I'd be inclined to suspect that things have only gotten to the point where a .xsession-errors would be created the one time.) Interesting. My guess is that there's a three step process here: delete .xsession-errors.old, move .xsession-errors to .xsession-errors.old, create a new version of .xsession-errors, one right after the other. Probably, but... Having no .old file makes it look like it crashed between steps one and two, which seems improbable. I do wish I knew what that meant! ...my guess is that once and only once has it even gotten to step 1. Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh, *not at all*. No login -- never even tries to start X (not as my user, anyway). I'm increasingly unconvinced that it has anything whatsoever to do with X. More like it can't start a login session. I'd guess that recovery mode does something that's just a bit different, as that is the *only* way I can get to a usable environment of any kind. (Hrm... on that note, it's interesting to note that the one and only GUI program I was able to try to run is Konsole... which tries to start a new pty and shell session immediately, i.e. isn't entirely unlike logging in a second time. I'd *almost* say it's starting the shell that's the trouble, except I'm not sure why that would work in emergency mode but not otherwise.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 16:29, Joe Zeff wrote: On 06/19/2015 01:13 PM, Matthew Woehlke wrote: I'm increasingly unconvinced that it has anything whatsoever to do with X. More like it can't start a login session. I'd guess that recovery mode does something that's just a bit different, as that is the*only* way I can get to a usable environment of any kind. Have you tried creating a new user? Yes. *No* user can log in. Not the user I created at install, not a newly created user, ***not root***. The only way I can interact with the system *in any way* is in emergency mode. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 17:27, Suvayu Ali wrote: In emergency mode, could you look at what logind was up to in the previous boot? Something like the following should work: # journalctl -b -1 -u systemd-logind You could compare with the current boot by switching the -1 to 0. Maybe this will give you clues. 16:47:38 New session c1 of user sddm. 16:47:56 New session 1 of user matthew. 16:48:24 Power key pressed. 16:48:24 Powering Off... 16:48:24 System is powering down. Nope, nothing interesting. Alas, because I can't log in, the only things I can do to debug are hope that log files get left. (Is there a way to start the VTY login handling *without* losing the emergency shell?) (@Joe, boot.log seems to just be the systemd startup output... nothing obvious there...) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 17:47, Joe Zeff wrote: There should also be a ~/.xsession-errors.old and with luck, it might have something in it. There isn't. (I'd be inclined to suspect that things have only gotten to the point where a .xsession-errors would be created the one time.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 17:46, Rick Stevens wrote: Maybe we can catch log entries before it completely dies. Bring the system up in single user mode, then edit /etc/systemd/journald.conf. Find the line: #ForwardToSyslog=no Change it to: ForwardToSyslog=yes and save the file. This should cause journald to forward log entries to the old system logger. Reboot and force the crash. Hopefully, the messages will get logged to /var/log/messages before you lose the log daemon. Haha... that's completely unhelpful as I *have* no /var/log/messages. Not that is in any way useful: Jun 19 14:30:51 gryphon rsyslogd-2027: imjournal: fscanf on state file `/var/lib/rsyslog/imjournal.state' failed [v8.8.0 try http://www.rsyslog.com/e/2027 ] That is THE ENTIRE FILE. (Well, that exact message a few times with various dates, plus a bunch of NUL's.) I'm starting to wonder about the disk(s)... though the OBD's¹ pass, which doesn't give a lot of ammunition to take to Dell's support. Anything else I can run to further diagnose, or better yet, confirm if there is a HW problem? (¹ Not useless-for-this-purpose POST, but the Dell OBD's that take several minutes to run just the basic tests.) Oh, and... apparently some update (or just additional use) made things worse; I can no longer VTY switch *at all* after a normal boot. (I'd be inclined to believe that the SSD went read-only or something, except I *can* apparently install updates - dnf succeeds, grub shows a new kernel - and /var is on the magnetic disk.) The only other message I can access is: snd_hda_intel :01:00.1 CORB reset timeout#2, CORBRP = 65535 Anything else is going into the bitbucket. The above *does* seem to happen right before the system dies, but it seems innocuous? BTW, this is *all without running X* (AFAIK)... the system freezes trying to go from single-user mode to 'systemctl start graphical.target' without ever seeing kdm start. (I do get kdm when booting normally; in that case, it's hitting enter after typing my password when the system freezes.) ...although in that case, freezes means the original TTY is no longer usable, but I can VTY switch (alt-f2) to another, log in, and get the last login... message, but no further. Same deal with ssh; I can get as far as the last login... message but never get a shell. This last time I also arranged to have a 'dmesg -w' running at the time; no output of any kind from that on login attempts. (On a different note, Fedora is also unable to reboot or power off this machine, although that's been par for the course with Dell Precision M's.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F22 unusable - system freezes on login
(First try apparently got eaten; apologies if this is a duplicate.) I just installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seemed to run okay, but when I try to boot the installed OS, it (almost¹) invariably freezes when I try to log in. The machine is effectively unusable as a result. Has anyone else encountered this? Can anyone recommend a course of diagnostics? I'm unable to even get the machine into a state that would allow remote login (over ssh anyway, and I don't know offhand how to set up serial login), and I've not seen anything in /var/log/messages that might indicate a problem. (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. does # df -h show enough space in root? / 108G /boot 336M /boot/efi 55M /var 119G /home 881G New system, remember? There's nothing on it but the initial install (modulo updates). I haven't even gotten to installing additional software that I'll eventually want, because the system is unusable ATM. if you can get in as single user you might look at journalctl to see what happened when it locks up Hmm... is it expected that there are no entries *at all* for the last few boots? The only entries I have are for June 5. (And yes, my system date is correct: June 18.) Anyway, I have no idea what I'd be looking for. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 12:54, Matthew Woehlke wrote: I just installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seemed to run okay, but when I try to boot the installed OS, it (almost¹) invariably freezes when I try to log in. The machine is effectively unusable as a result. HEY! Turns out I *really can't log in*! I managed to persuade the machine to bring the network up on startup, and *I can't log in remotely either*. Same symptoms; as soon as I try, the machine locks up. KDM remains more or less responsive, but TTY switching, which would otherwise work, results in a permanently black screen. Oh... and /var/log/messages isn't actually just unhelpful, it's *corrupt*... both less and vi show a bunch of '^@' special characters where recent log entries ought to be. I have (many) entries from June 5, then one or two fragments from June 14 and again from today... but literally just a few lines, *nothing* like the hundreds of lines I *should* have from a normal boot-up. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 17:16, Rick Stevens wrote: On 06/18/2015 01:52 PM, Matthew Woehlke wrote: On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. Then you definitely have a graphics issue. Bring it up in single user mode and have a look at the /var/log/Xorg.0.log file to see if there's anything that might point to an issue. I had an issue on one machine with nouveau on a specific video card. Using an nVidia binary blob driver overcame that. It's an AMD (GPU, not CPU). Anyway, I am allergic to proprietary software :-). Nothing in any of the Xorg.*.log*'s jumps out at me. ~user/.xsession-errors is empty. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
