Hey folks, I'm calling this a beta!

softbear · 09-23-2013, 08:49 AM

Thanks to Patrick and the Team!

First look: it just works, as usual.

Now to add all my other favorite stuff and see what breaks...

Habitual · 09-23-2013, 09:06 AM

Quote:

Originally Posted by rkfb

There is a 64-bit Skype at Slacky with the 32-bit libraries built in.

http://www.slacky.eu/asche64/pkgs/in...er=16&pkg=2111

Thanks Robert.
I've been diligent about not mixing sources up to now, keeping with "if it isn't broke..."

AlleyTrotter · 09-23-2013, 09:40 AM

current dated Mon Sep 23 00:32:58 UTC 2013

There was nothing special about the install
gpt partitioned disk
/dev/sdb1 efi partition mounted at /boot/efi
/dev/sdb4 linux partition mounted at /
/dev/sdb9 swap partition

install finished successfully then I

cp /mnt/boot/vmlinuz-huge-3.10.12 /mnt/boot/efi/bzImage-huge

boot into Shellx64.efi ( this shell is either built into the bios or installed in an efi partition )

at the efishell prompt
fs1: [enter] puts you in dev sdb efi partition
"bzImage-huge root=/dev/sdb4 ro console=ttys0 [enter]"
boots /dev/sdb4 in UEFI mode
afterlogging in as root do
"modprobe efivars"

from here you can use
efibootmgr to create an elilo boot option
cp /boot/elilo-x86_64.efi /boot/efi/elilo.efi
create /boot/efi/elilo.conf containing

Code:

prompt
timeout=50
default=huge

image=bzImage-huge
  label=huge
  read-only
  root=/dev/sdb4

"efibootmgr -c -d /dev/sdb -l elilo.efi -L linuxB -p 1"

or grub-install to create a grub boot option
grub-install --target=x84_64-efi \
--efi-directory=/boot/efi \
--bootloader-id=slackware \
--recheck \
--debug \
--force
if no errors then
grub-mkconfig -o /boot/grub/grub.cfg

Actually you can probably do both whichever one you do last becomes
the default boot.
They both would showup in the UEFI boot manager screen

Hope and pray there are no typo's above
John

PS my lspci for reference

Code:

00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.3 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 4 (rev c4)
00:1c.4 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 5 (rev c4)
00:1c.5 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 6 (rev c4)
00:1c.7 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 8 (rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
02:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57781 Gigabit Ethernet PCIe (rev 10)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller

rvdboom · 09-24-2013, 12:39 AM

Quote:

Originally Posted by Didier Spaier

At boot time, when you see lilo's screen hit [Tab], and complete your command line, e.g.

Code:

Linux 3

Of course you can set any kernel or modules parameters that way.

But you cannot manually change the name of the kernel image you boot that way, can you?
Changing the command line to boot /boot/3.9.1 instead of /boot/3.10.2?

If it's possible, I'm a complete ass. :-)

Didier Spaier · 09-24-2013, 02:06 AM

Quote:

Originally Posted by rvdboom

But you cannot manually change the name of the kernel image you boot that way, can you?
Changing the command line to boot /boot/3.9.1 instead of /boot/3.10.2?

You can only if there's a stanza in lilo.conf for each kernel image of course, and if you edit lilo.conf to add one, you'll have to run "lilo" once
to install it. Afterwards you can change it at boot time.

phenixia2003 · 09-24-2013, 05:06 AM

Hello,

According to this section on that page, since version 1.6, Wine needs libOSMesa which only requires to build Mesa with option --enable-osmesa.

On the same page, there's also a note on the new dependency required by Wine 1.7 : Little CMS. Therefore, the package lcms2 should be added to the multilib.

--
SeB

jtsn · 09-24-2013, 10:54 AM

Quote:

Originally Posted by AlleyTrotter

or grub-install to create a grub boot option
grub-install --target=x84_64-efi \
--efi-directory=/boot/efi \
--bootloader-id=slackware \
--recheck \
--debug \
--force
if no errors then
grub-mkconfig -o /boot/grub/grub.cfg

There GRUB package is not very polished its current state:

GRUB_SAVEDEFAULT=true isn't working. /boot/grub/grubenv gets updated, but the saved entry doesn't get selected, it always boots the first menu entry.

/etc/grub.d/10_linux generates menu entries called "Slackware GNU/Linux", which isn't the name of my favorite distribution. Slackware isn't a GNU project, but a commercial distribution.

/etc/grub.d/10_linux doesn't understand Slackware kernel file names. It assumes that the version number follows behind the first dash of /boot/vmlinuz. So it sees "huge-3.10" and "generic-3.10" as version number. It then compares these strings with determine the "latest and greatest" for the default selection and sorts them alphabetically. So it prefers "huge" over "generic", just because "h" is behind "g" in the alphabet.

/etc/grub.d/30_osprober isn't able to detect any operating systems on an EFI system, because their bootloaders reside inside the EFI directory on the ESP. Also GRUB in EFI mode isn't able to boot any legacy operating systems, so even if the script finds some of them, the menu entries wouldn't work.

TobiSGD · 09-24-2013, 12:53 PM

Quote:

Originally Posted by jtsn

/etc/grub.d/10_linux generates menu entries called "Slackware GNU/Linux", which isn't the name of my favorite distribution. Slackware isn't a GNU project, but a commercial distribution.

You should educate yourself about the term GNU/Linux.

Didier Spaier · 09-24-2013, 01:21 PM

I think that jtsn is right. Project's name is The Slackware Linux Project, as shown on its home page and distributions's name is Slackware Linux. And AFAIK its founder didn't put it under the GNU umbrella.

TobiSGD · 09-24-2013, 01:30 PM

Calling it GNU/Linux does not at all mean that Slackware is a GNU project: https://en.wikipedia.org/wiki/GNU/Li...ng_controversy

Didier Spaier · 09-24-2013, 01:49 PM

Patrick Volkerding names it Slackware Linux. In my opinion if you want to name it differently you should ask him. At the bottom of the home page I read:

Quote:

Slackware® is a registered trademark of Slackware Linux, Inc.

astrogeek · 09-24-2013, 03:02 PM

I try to credit GNU when referring to Linux generically: GNU/Linux.

But I too think that Slackware GNU/Linux is not appropriate (at least unnecessary overkill).

This is not an exact analogy, but when flying I might refer to my ride as a Delta 757, while speaking of the aircraft generically as a Boeing 757.

I Would not refer to my flight as a Delta Boeing 757.

volkerdi · 09-24-2013, 03:29 PM

If GRUB (a GNU project) wants to call all Linux distributions GNU/Linux, who am I to change that? And if Slackware wants to call itself Linux, why should GNU demand otherwise?

It's all about the freedom.

astrogeek · 09-24-2013, 03:59 PM

Quote:

Originally Posted by volkerdi

If GRUB (a GNU project) wants to call all Linux distributions GNU/Linux, who am I to change that? And if Slackware wants to call itself Linux, why should GNU demand otherwise?

It's all about the freedom.

I've seen that somewhere before...

Yes it is, without that, everything else is just spraying in the wind!

AlleyTrotter · 09-24-2013, 06:26 PM

Has anyone tried my method of getting Slackware Current running in UEFI mode?
Hasn't it worked for anybody?
Or did everyone already know this?
Just Asking
John