Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
on troubles installing Slackware 14.0, 64-bit, and skipping lilo installation
48 views
Skip to first unread message
Marco Maggi
May 25, 2013, 9:48:59 AM5/25/13
to
Ciao,
in the last days I have installed Slackware 14.0, 64-bit,
on a new notebook running Microsoft Windows 8. AFAICT I now
have a UEFI dual-booting notebook with Windows and
Slackware.
Before booting from "usbboot.img" I had already
partitioned the hard disk and created the file systems.
While running the setup program I skipped the installation
of lilo, which is not used by UEFI boot.
Unless I have made some mistake (which is possible given
that I had a rough fight to get the UEFI boot process
working (it was my first time with this technology)), this
left me with an unusable Slackware installation: for some
reason the "/etc/fstab" file had not been created, which
caused the first Slackware boot to stop with:
e2fsck: / is a directory
or similar. After writing a "fstab" by hand, the system
booted correctly. However I had to reinstall the "udev"
package because some of the devices were not there (I
noticed a missing "/dev/audio"); after this there seems to
be no other problem I can tell apart from the usual
post-setup configuration.
So I wonder:
* Is the hard disk prepartitioning and preformatting, or
skipping lilo the cause of troubles like a missing
"/etc/fstab"? I am sure to have correctly selected the
partitions to be mounted while running "setup".
* Is a failure to do the first Slackware boot the possible
cause of missing devices?
Also: is there some plan by the Slackware maintainers to
support UEFI boot?
TIA
--
"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"
in the last days I have installed Slackware 14.0, 64-bit,
on a new notebook running Microsoft Windows 8. AFAICT I now
have a UEFI dual-booting notebook with Windows and
Slackware.
Before booting from "usbboot.img" I had already
partitioned the hard disk and created the file systems.
While running the setup program I skipped the installation
of lilo, which is not used by UEFI boot.
Unless I have made some mistake (which is possible given
that I had a rough fight to get the UEFI boot process
working (it was my first time with this technology)), this
left me with an unusable Slackware installation: for some
reason the "/etc/fstab" file had not been created, which
caused the first Slackware boot to stop with:
e2fsck: / is a directory
or similar. After writing a "fstab" by hand, the system
booted correctly. However I had to reinstall the "udev"
package because some of the devices were not there (I
noticed a missing "/dev/audio"); after this there seems to
be no other problem I can tell apart from the usual
post-setup configuration.
So I wonder:
* Is the hard disk prepartitioning and preformatting, or
skipping lilo the cause of troubles like a missing
"/etc/fstab"? I am sure to have correctly selected the
partitions to be mounted while running "setup".
* Is a failure to do the first Slackware boot the possible
cause of missing devices?
Also: is there some plan by the Slackware maintainers to
support UEFI boot?
TIA
--
"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"
Michael Black
May 25, 2013, 11:38:37 AM5/25/13
to
I routinely make a partition (and maybe format it) before installing
Slackware. It notices that there are some existing partitions, asked if
I want to use them.
The installer can't move forward until you specify a partition to install
to, so it can't be that you clicked something too fast.
Likewise, plenty of times, I've deal with lilo later. (And definitely
lilo would have nothing to do with fstab).
I cna't see how you got an install without udev or fstab.
Michael
0 new messages