![]() |
Good evening. Sorry I'm late in responding. I did not get online last night.
O.k. So, I tried the suggestions you guys provided. 1. I started Slackware from the installation DVD using the following suggested by onebuck: Code:
Boot: huge.s root=/dev/sda5 initrd=ro nomodeset Quote:
2. As requested by onebuck, here are the contents of the Slackware '/etc/lilo.conf' file: Code:
# LILO configuration file Quote:
4. I retried the code provided by Didier, and verified that I typed it just as directed (with upper case X in Xorg): Code:
mount /dev/sdb1 /mnt Quote:
5. To answer the question posed by Didier: Quote:
6. To answer the other questions posed by Didier: Quote:
Perhaps I need to be a little more specific when I say that I receive a "black screen". Yes, I do see a full screen of code flash by just prior to the "black" screen; however, it scrolls so quickly that I cannot read it. Also, the screen is not completely black, such as when the display is turned off, or when Windows is in Hibernation mode. The screen technically appears as a slightly back-lit grey/black color just as when the computer begins booting from BIOS when initially turned on. 7. Drakeo mentioned that the problem could possibly be loading 64-bit Slackware onto a 32-bit machine. I don't think this would be the problem, since I run Windows 7 64-bit on it. I sincerely appreciate all of the energy you guys are expending in assisting me in getting Slackware running! |
Thanks for your precise answers that really help investigate.
Maybe, the black screen is linked to the lack of a line beginning with "kernel driver in use" in the output of the lspci command. I have three more questions to investigate further. 1. What is the output of following commands (once logged in your system as root): Code:
modprobe i915 #output should be empty 3. Did you check the integrity of the Slackware ISO image before burning it to the USB stick? If not please do that. I remind you that the check-sum .md5 files for each Slackware DVD ISO image are available in the same directory as the ISO image itself, in a sub-directory of http://mirrors.slackware.com/slackware/slackware-iso/ Oh and a small remark: you could have used the Slackware installer itself to run cfdisk, it contains this utility among other ones. |
It has been reported that the HP G72 may require the 'acpi_backlight=vendor' kernel parameter. http://www.linuxquestions.org/questi...7/#post4645378
To test this, you could boot from the install disk and use Code:
huge.s root=/dev/sda5 initrd=ro acpi_backlight=vendor Code:
append=" vt.default_utf8=0 acpi_backlight=vendor" |
Hi, Didier.
1. I ran the code as you instructed: Code:
modprobe i915 #output should be empty The output to the second command is as follows: Code:
i915 567446 0 Quote:
3. Quote:
------- Hi, allend. I tried the code you provided: Code:
huge.s root=/dev/sda5 initrd=ro acpi_backlight=vendor |
The lack of output in /var/log/Xorg.0.log is strange. There should at least be information on the version of the X.Org X Server in use.
Is the D-bus message service available? i.e. is /etc/rc.d/rc.messagebus an executable file If you have been able to configure networking, then you could use slackpkg to check your installation for missing packages. Type 'man slackpkg' for further information. |
Quote:
|
Quote:
|
allend:
Quote:
Didier: Quote:
|
Any suggestions? Still need help!
Thanks! |
Quote:
I suggest installing LILO to the MBR so that you have a multiboot setup. 1. Boot from the install media and continue till you are logged in as root. 2. Mount your Slackware partition with 'mount /dev/sda5 /mnt' 3. Take a copy of the first track of your disk with 'dd if=/dev/sda of=/mnt/boot/track0.img bs=512 count=63' 3. Test installing LILO to the MBR with 'lilo -r /mnt -M /dev/sda -t' 4. If all looks OK, install LILO to the MBR with 'lilo -r /mnt -M /dev/sda' I understand your concern about protecting your Windows setup, but installing LILO to the MBR is what I have always done and I have never experienced any problems. If a disaster occurs, then your options include: a) use the Windows repair function to recover e.g. http://www.tomshardware.com/news/win...mbr,10036.html. b) restore disk track 0 by following steps 1 and 2 above, then 'dd if=/mnt/boot/track0.img of=/dev/sda'. c) restore the copy of the first sector of the disk (containing your disk partition table) that LILO placed in the /boot directory using dd. |
Good evening. My apologies for taking so long in reposting. My graduate school semester began and I had to put getting Slackware running on the backburner - only so many hours in a day with little sleep. :-)
So, now that my semester is over and we're through the Christmas holidays, I'm back trying to get Slackware running on my laptop. I finally stopped being hard-headed and took the advice many of you gave - I loaded LILO to the Master Boot Record. To do so, I used the process provided by allend: Quote:
Quote:
Quote:
I even tried re-running cfdisk and changing sda5 partition to bootable, instead of sda1. However, when I restarted the computer it were as if the BIOS couldn't find the bootable partition. I received a message stating that there was not a bootable partition. I re-ran cfdisk, changed sda1 partition back to be bootable, and restarted the computer. It boots straight into Windows 7 again. As a recap, here's my lilo config file contents: Quote:
Thanks! |
Quote:
Code:
# Start LILO global section BTW - You may also want to add these lines to the global section of your /etc/lilo.conf. Code:
lba32 # Allow booting past 1024th cylinder with a recent BIOS |
Hi, allend.
I edited the lilo.conf file as you directed. In the LILO global section I changed: Code:
boot = /dev/sda Code:
lba32 Code:
lilo -r /mnt -M /dev/sda Now... I did initially make a typing mistake. When I first typed the lilo command, I accidently hit the enter key before typing the rest of the command (immediately after the word lilo). So, I reentered the full line lilo -r /mnt -M /dev/sda again. Did my typing mistake mess something up? |
When you are in the chroot environment, just type 'lilo'.
|
Ahhh. Ok.
Will that still make LILO write to the Master Boot Record? |
All times are GMT -5. The time now is 02:15 PM. |