LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Dell Inspiron 1520 Laptop locks up after slack64 14.1 install (http://www.linuxquestions.org/questions/slackware-installation-40/dell-inspiron-1520-laptop-locks-up-after-slack64-14-1-install-4175494269/)

SAJM 02-08-2014 11:35 AM

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.

The laptop is now bricked.

The last thing on the screen prior to lock up is:

[ 3.653043] [<ffffffff81b4b9f0>] ? rest_init+0x80/0x80

Didier Spaier 02-08-2014 02:37 PM

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.

SAJM 02-08-2014 04:35 PM

Quote:

Originally Posted by Didier Spaier (Post 5114079)
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.

Didier Spaier 02-08-2014 05:03 PM

Quote:

Originally Posted by SAJM (Post 5114140)
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.

To narrow down the problem, can you boot your other computer off the same USB stick?

SAJM 02-08-2014 06:06 PM

Quote:

Originally Posted by Didier Spaier (Post 5114149)
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.

Didier Spaier 02-09-2014 02:04 AM

Quote:

Originally Posted by SAJM (Post 5114168)
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.

SAJM 02-09-2014 09:54 AM

Quote:

Originally Posted by Didier Spaier (Post 5114323)
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.

Didier Spaier 02-09-2014 10:28 AM

Reinstall. When asked, choose an ext4 file system, then "check => Slow format that checks for bad blocks".

SAJM 02-09-2014 02:27 PM

Quote:

Originally Posted by Didier Spaier (Post 5114461)
Reinstall. When asked, choose an ext4 file system, then "check => Slow format that checks for bad blocks".

I did that. When it came to configuring LILO it said there was a problem with the display and LILO.

I can boot boot to a point but get the following error:

"The superblock could not be read" together with lots of stuff about ext2.

I then get a choice of entering contrl-d or give root pwd for normal log in. both options just reboot the system

The USB stick created during the install turns out to be unbootable.

TobiSGD 02-09-2014 02:45 PM

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).

SAJM 02-09-2014 05:45 PM

Quote:

Originally Posted by TobiSGD (Post 5114570)
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.

TobiSGD 02-09-2014 06:27 PM

Quote:

Originally Posted by SAJM (Post 5114636)
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.

ReaperX7 02-19-2014 02:20 AM

Hard drives are easily replaced. If it's the hard drive just get a replacement and all will be well.

As far as partitioning... I suggest either:

/(root) - ext4
Swap - 2x your RAM

Or...

/boot - ext4 - 50mb
/(root) - JFS or BtrFS - remaining space
Swap - 2x your RAM

TobiSGD 02-19-2014 05:05 AM

Why would you recommend swap to be 2x RAM?

ReaperX7 02-19-2014 09:39 PM

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.


All times are GMT -5. The time now is 12:05 AM.