Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
Hi, I been looking around in this forum for awhile and I finally decided to try out Slackware. I bought the product from slackware store, the official book and followed the exact installation instruction but I'm getting a error called:
Quote:
PXE E53: No boot file name received.
PXE-M0F: Exiting Intel Boot Agent.l
No bootable device -- insert boot disk and press any key.
I installed LILO to the MBR (linux is the only OS on this pc). I change the boot sequence to HDD first and tried various boot sequence without any luck.
The OP of that thread said he fixed it by doing:
Quote:
I recreate the lilo.conf using liloconfig in /sbin folder. it works .
Also, I change the boot sequences.
I'm not sure how this is done. I can't log in or anything, I created the USB boot stick but I'm not sure how to work that.
I'm not sure if it matters but I installed slackware by # fdisk /dev/sda. The guide told me to do # fdisk /dev/hda but I couldn't write on it (read-only). After typing # fdisk /dev/sda, I was able to write on it and delete the previous partition as well.
I did a google search and found out I need to disable the "boot by network." After I did this and rebooted, my computer has a black screen with a "_" that is blinking (don't include the " "). It keeps blinking and nothing happens.
I'm not sure if this would matter but I'll list down the BIOS menu:
Quote:
Computer: Gateway 507GR
Main Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz
DRAM frequency: 400 HHz
Total memory: 2560 MB RAM
Cache size: 1024 KB
Product name: 507GR
BIOS Version: AG91510J.15A.0816.2005.0214.1818
CD/DVD-ROM Drive order
<_NEC DVD_RW ND-3>
<LITE-ON DVD SOHD>
Removable Drive order: No removable Drive
Boot to Optical devices <enabled>
Boot to Removable Devices <enabled>
Boot to Network <enabled> (turning this off with everything else with default configuration causes the black screen with this sign blinking forever: _ )
USB Boot <enabled>
Quote:
Advanced Tab
Peripheral configuration
Parallel port <enabled>
Mode <Bi-directional>
Audio <Enabled>
Legacy front Panel Audio <enabled>
On-board LAN <enabled> (turning this off with everything else with default configuration causes the black screen with this sign blinking forever: _ )
Onboard 1394 <enabled>
PCI Latency Timer <32>
There's more but I'm not sure if those are necessary. Thank you for reading.
Hi, I been looking around in this forum for awhile and I finally decided to try out Slackware. I bought the product from slackware store, the official book and followed the exact installation instruction but I'm getting a error called:
I installed LILO to the MBR (linux is the only OS on this pc). I change the boot sequence to HDD first and tried various boot sequence without any luck.
The OP of that thread said he fixed it by doing:
I'm not sure how this is done. I can't log in or anything, I created the USB boot stick but I'm not sure how to work that.
I'm not sure if it matters but I installed slackware by # fdisk /dev/sda. The guide told me to do # fdisk /dev/hda but I couldn't write on it (read-only). After typing # fdisk /dev/sda, I was able to write on it and delete the previous partition as well.
I did a google search and found out I need to disable the "boot by network." After I did this and rebooted, my computer has a black screen with a "_" that is blinking (don't include the " "). It keeps blinking and nothing happens.
I'm not sure if this would matter but I'll list down the BIOS menu:
There's more but I'm not sure if those are necessary. Thank you for reading.
The PXE message means that the system tried to boot from the hard disk but failed, and then tried to boot from the network. Booting from the network will not work if you did not configured pxe and tftp on a server (which you probably don't want to in your case).
So actually it was not possible to boot from hard disk.
Is the correct partition set active? I recommend using grub as it is more flexible.
Is fdisk the only thing you did?
If so, you created a partition but that is not necessarily bootable.
GateWay 9310X Desktop, Installed Slackware12.2 last night.
I have same "PXE -E53 No Bot File name received BC-Loader() ==0053".
Switch How did You disabled the "boot by network"? Google results did not match my bios.
I pretty sure I set /sda1 to boot in Lilo. Should I be using /dev/hda instead of /dev/sda? (Do I need to create my own thread? Thought since same problem why waste space?)
GateWay 9310X Desktop, Installed Slackware12.2 last night.
I have same "PXE -E53 No Bot File name received BC-Loader() ==0053".
Switch How did You disabled the "boot by network"? Google results did not match my bios.
I pretty sure I set /sda1 to boot in Lilo. Should I be using /dev/hda instead of /dev/sda? (Do I need to create my own thread? Thought since same problem why waste space?)
Just go into your bios and try to search for "boot order" or a menu where you can choose: hard disk/cdrom/ethernet1/...
If you know your boot order and PXE (ethernet) is after hard disk in the list, then it was not able to boot your OS. Your partition to boot from should be active (you can see this in fdisk, it is the row that has a * in it.) and your bootloader should be correct.
sda will be used for sata disks while hda is for IDE disks.
But If I understand you correctly you don't get anything to see from lilo? And lilo should be the first part that starts. So first check if lilo is installed correctly. Also I would recommend to install grub as you don't have to "install" changes. You can use the prompt and can determine what the correct parameters are this way.
Thank u deadeyes, I chked boot order, I get nothing frm lilo on boot. In /boot i see boot .800, vmlinuz and kernels are there sysmap.. I looked in /etc/lilo.conf In fdisk table I see a plus after the end blocks for sda1. I don't know how to use grub, sorry Cld not having a video card driver cause this problem?
Thank u deadeyes, I chked boot order, I get nothing frm lilo on boot. In /boot i see boot .800, vmlinuz and kernels are there sysmap.. I looked in /etc/lilo.conf In fdisk table I see a plus after the end blocks for sda1. I don't know how to use grub, sorry Cld not having a video card driver cause this problem?
As for the video card: I think this is not the case. There are some standards that each monitor should be able to do.
I would like to help you, but I almost have no lilo experience.
Are you aware that the config you made in (I think) /etc/lilo.conf should be installed? Did you execute "lilo" after configuring the bootloader?
If your bootloader is working correctly I don't think you need the correct active partition. But if it is not there should be started from the active partition (note that the + you are talking about is not the active partition; there should be a * in the 2nd column; with "a" in fdisk you can do this, this should be the boot mountpoint I think).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.