Dell Inspiron 1520 Laptop locks up after slack64 14.1 install
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Dell Inspiron 1520 Laptop locks up after slack64 14.1 install
I loaded as described in the title and when booting the process gets to a certain stage and locks up with Caps lock flashing. I tried to reboot using a USB stick and that is no longer recognised by the laptop.
Check in the BIOS that it still be set up to boot off an USB device first and see if you can boot off your USB installer (as if you'd install again). If yes we can tell you how to chroot into you slackware and reinstall lilo.
Anyhow, as the boot sequence aborts after more that 3.5 seconds, I don't think that the laptop is actually bricked.
Check in the BIOS that it still be set up to boot off an USB device first and see if you can boot off your USB installer (as if you'd install again). If yes we can tell you how to chroot into you slackware and reinstall lilo.
Anyhow, as the boot sequence aborts after more that 3.5 seconds, I don't think that the laptop is actually bricked.
I have set it to boot off USB and it doesn't see the stick. I do however have PXE working but I can never get anything to run using PXE.
Last edited by SAJM; 02-08-2014 at 04:42 PM.
Reason: Spelling
To narrow down the problem, can you boot your other computer off the same USB stick?
I was not clear earlier. The USB stick contained the recovery data generated when I did the install. I have just reloaded it using the default install kernel and I have my Dell laptop back booting by USB. However I still haven't a clue how to go about fixing lilo, short of doing yet another fresh install.
I have just reloaded it using the default install kernel and I have my Dell laptop back booting by USB.
I assume that you mean you can boot off the USB stick containing the installer (the one you have put on it using the "dd" command, see your other thread).
If that is that case, just do what are told on the first screen to boot your already installed Slackware:
Code:
In a pinch, you can boot your system from here with a command like:
boot: hugesmp.s root=/dev/sda1 rdinit= ro
In the example above, /dev/sda1 is the / Linux partition.
After booting, log in your Slackware as root, type "nano /etc/lilo.conf" to check and edit this file as need be, run "lilo -t -v" and il all goes well run "lilo", then remove the USB stick and reboot. That's all there is to it.
Last edited by Didier Spaier; 02-09-2014 at 02:05 AM.
In the example above, /dev/sda1 is the / Linux partition.[/CODE]After booting, log in your Slackware as root, type "nano /etc/lilo.conf" to check and edit this file as need be, run "lilo -t -v" and il all goes well run "lilo", then remove the USB stick and reboot. That's all there is to it.
I booted up as you suggested only used the huge.s kernel.
The script ran and loaded as before stopping and locking up at the same place.
There is a string of data scrolling, things like "no filesystem could mount root", "kernel panic", "unable to mount root"
If I let the startup script nun the default script I get access to root.
I entered the following:
slack:/# mount /dev/sda1 os
slack:/# block device is write protected , mounting read-only
then I got long hex strings
XFS (sda1): Internal error xfs_sb_read_verify at line730 of file fs/xfs/xfs_mount.c. Caller )xffffffff8134df45
XFS (sda1): corruption detected. Unmount and run xfs_repair
mount: you must specify the file system
I tried to run xfs_repair but did not understand it enough to feel confident.
At this point I would suspect hardware error and at least check the memory (using Memtest86+, can be found on the Slackware install DVD) and the harddisk (using the disk manufacturer's diagnosis tool).
At this point I would suspect hardware error and at least check the memory (using Memtest86+, can be found on the Slackware install DVD) and the harddisk (using the disk manufacturer's diagnosis tool).
Sadly you are correct. I ran the hard drive diagnostics and got error 2000-0146 which is bad news for the drive.
It was a 2nd hand computer and not worth repairing, so I guess it's all over. Thanks for everyone's help.
Sadly you are correct. I ran the hard drive diagnostics and got error 2000-0146 which is bad news for the drive.
It was a 2nd hand computer and not worth repairing, so I guess it's all over. Thanks for everyone's help.
I would not consider this computer to be too old for repairing (typing this on a laptop with somewhat similar specs that just a few months ago got a new SSD), but of course that is up to you.
Just something I learned a long time ago. Can't recall where, but the guy who told me it said always do double your RAM, unless you have over a certain size and amount, of which I forget just in case, but it had to deal with how much swap could be accessed should the need arise, but over a certain amount was unnecessary as it's just eaten up HDD space.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.