SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is not Slackware specific and not an error - but an annoyance I'd like to fix.
I have just received a nice new machine (new to me anyway!) and am about to install Slackware 14-64 on it.
It has W7 installed on a 320GB WD drive, and I have successfully used a GParted live CD to shrink the NTFS partition to 40GB and prepared partitions for my Slackware installation. Everything works as far as I can tell.
My preference is to install from PXE on my LAN. I have a PXE server running and have verified it is working by booting another box from it.
But my new machine steadfastly refuses to boot from the LAN even though it appears to support it. I have tried all the obvious choices from the CMOS setup and have verified the device is working on my LAN under W7.
In the Phoenix BIOS setup I find the following:
Under Advanced BIOS Features >> Hard Disk Boot Priority
1. Legacy LAN
3. Hard Disk
There is also an option for "Boot Other Device" with choices of enable and disable - set to Enable.
Then, under Integrated Peripherals I have "PCI LAN boot ROM" set to Enabled.
Moving the CDROM ahead of the hard disk in the boot order does allow me to boot from CD, but the LAN boot is simply ignored, and I see no boot messages at all indicating it was tried and failed.
Curiously, removing the hard disk from the list entirely is also ignored - it still boots to the disk.
Any Phoenix BIOS gurus out there with an insight?
The machine is about 2 years old, no-brand custom build, AMD Phenom II X2 3.1Ghz, WD 320GB PATA, Nvidia nForce ethernet plus Ralink RT2800 80211.n.
Is it possible that the wireless device could mask the ehternet LAN at this stage?
Tip for the future: If you have a question that is not related to Slackware, but for example to hardware, like in this case, put it in the Hardware forum.
There is no need to clutter up the Slackware forum with non-Slackware questions.
Please mark this thread as solved using the thread tools at the top of the thread.