Re: [lfs-support] Booting from EFI Hints

2017-05-27 Thread Alan Feuerbacher

On 5/27/2017 6:55 PM, Wayne Blaszczyk wrote:


Just out of interest, can you run the lspci command and tell me how many USB 
controllers you have?
I only have one.

00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller


Two: Intel Z270 Chipset and ASMedia USB 3.1. See below.


This is despite the specs of my motherboard saying.

Intel® Z270 Chipset :
8 x USB 3.0 port(s) (4 at back panel, blue, Type-A, 4 at mid-board)
Intel® Z270 Chipset :
6 x USB 2.0 port(s) (2 at back panel, , Type-A, 4 at mid-board)


My specs are nearly the same, except there are 6 USB 3.0 and 8 USB 2.0, 
all listed under Intel Z270 Chipset.



Also, execute 'lsusb -t'.
This will show which Bus Driver the port in question falls under.



###
root [ ~ ]# lspci
00:00.0 Host bridge: Intel Corporation Device 591f (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 5912 (rev 04)
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:17.0 SATA controller: Intel Corporation Device a282
00:1b.0 PCI bridge: Intel Corporation Device a2e7 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a290 (rev f0)
00:1c.1 PCI bridge: Intel Corporation Device a291 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2c5
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.3 Audio device: Intel Corporation Device a2f0
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) 
I219-V
03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network 
Connection (rev 03)

04:00.0 USB controller: ASMedia Technology Inc. Device 2142
###


###
root [ /sources/usbutils-008 ]# lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 7: Dev 2, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 7: Dev 2, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 8: Dev 3, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M

|__ Port 13: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
##


--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-27 Thread Wayne Blaszczyk
On Sat, 2017-05-27 at 12:16 -0600, Alan Feuerbacher wrote:
> On 5/26/2017 3:37 AM, Wayne Blaszczyk wrote:
> > On Thu, 2017-05-25 at 10:52 -0600, Alan Feuerbacher wrote:
> > > Since yesterday, I installed quite a bit more BLFS software, plus the
> > > rEFInd boot manager from RodsBooks. Sendmail is now installed.
> > > 
> > > LFS seems to boot up to the "komodo login:" prompt, and then hangs.
> > > Every kernel message shows [ OK ] on the right side of the screen. The
> > > last is for "Starting sendmail". The NIC seems to come alive.
> > 
> > I had the same issue and and turned out to be USB3 was not enabled during 
> > the kernel build.
> > 
> > Make sure that CONFIG_USB_XHCI_HCD is enabled.
> > Or plug the keyboard into a USB2 port if you have one?
> 
> I enabled that, along with all of the CONFIG stuff that I could find in 
> the BLFS Index of kernel-related software.
> 
> See my email of a few minutes ago for details.
> 
> A mystery is what exactly fixed the problem. I have both keyboard and 
> mouse plugged into USB2 ports on the MB, so I don't see what enabling 
> CONFIG_USB_XHCI_HCD could have done.
> 
> Thanks!
> 
> Alan
> 

Just out of interest, can you run the lspci command and tell me how many USB 
controllers you have?
I only have one.

00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller

This is despite the specs of my motherboard saying.

Intel® Z270 Chipset : 
8 x USB 3.0 port(s) (4 at back panel, blue, Type-A, 4 at mid-board)
Intel® Z270 Chipset : 
6 x USB 2.0 port(s) (2 at back panel, , Type-A, 4 at mid-board)

Also, execute 'lsusb -t'.
This will show which Bus Driver the port in question falls under.

Regards,
Wayne.




-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-27 Thread Ken Moffat
On Sat, May 27, 2017 at 12:11:15PM -0600, Alan Feuerbacher wrote:
> Success! I've managed to boot LFS 8.0, X Windows, Firefox and Thunderbird.
> 
> I've learned a lot about Linux from this, especially how to boot with an EFI
> bios and GTP partitions.
> 
> On 5/25/2017 2:32 PM, Ken Moffat wrote:
> > On Thu, May 25, 2017 at 12:30:56PM -0600, Alan Feuerbacher wrote:
> > > On 5/25/2017 12:24 PM, Kuba wrote:
> > > > On Thu, 25 May 2017 12:19:53 -0600, Alan Feuerbacher
> > > >  wrote:
> > 
> > First, may I suggest that sendmail is probably not a mail server
> > which many people want to use.  It used to be horrendous to
> > configure.  I run postfix, which provides /usr/sbin/sendmail.
> 
> I looked into installing that, but on first glance it looks like a lot of
> work configuring it. Comments?
> 
> Now that Thunderbird is working, do I need Postfix?
> 
> > Just mentioning that in case it is something in sendmail that is
> > hanging.
> 
> Turns out sendmail was working ok. But I've disabled it.
> 

All depends what you want to do for mail :)  I keep mail in mboxes
on the machine designated as my server.  I run fcron jobs ln the
other machines (SMART status, periodic log rotation, first-stage
backups) and hope to send the mail to the server where I can read
it.  From time to time things end up in /var/mail on the desktop
boxes.

If thunderbird does all you need then you don't need postfix or
sendmail.

ĸen
-- 
I live in a city. I know sparrows from starlings.  After that
everything is a duck as far as I'm concerned.  -- Monstrous Regiment
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-27 Thread Alan Feuerbacher

On 5/25/2017 10:30 PM, Michael Shell wrote:

On Thu, 25 May 2017 10:52:28 -0600
Alan Feuerbacher  wrote:


Grub, which loads vmlinuz-4.9.9-lfs-8.0
rEFInd, which loads grub, which loads vmlinuz-4.9.9-lfs-8.0
Each of the two methods results in the same kernel startup messages and
then a hang.


I would try booting directly to a root shell using grub:

https://askubuntu.com/questions/15284/how-to-boot-to-root-shell-when-grub-recovery-menu-fails-to-load-a-shell

linux init=/bin/sh

This way, you should be able to isolate kernel/keyboard problems from
system setup problems.


I tried that. Actually I had tried more or less the same thing before, 
since my MB bios allows booting directly into a shell.efi of some sort. 
It all failed, which seems to have been because something was wrong with 
the kernel as compiled. Enabling various CONFIG parameters, as I said in 
emails a few minutes ago, along with a few minor fixes to NIC stuff, 
seems to have done the trick.


Alan

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-27 Thread Alan Feuerbacher

On 5/26/2017 3:37 AM, Wayne Blaszczyk wrote:

On Thu, 2017-05-25 at 10:52 -0600, Alan Feuerbacher wrote:

Since yesterday, I installed quite a bit more BLFS software, plus the
rEFInd boot manager from RodsBooks. Sendmail is now installed.

LFS seems to boot up to the "komodo login:" prompt, and then hangs.
Every kernel message shows [ OK ] on the right side of the screen. The
last is for "Starting sendmail". The NIC seems to come alive.


I had the same issue and and turned out to be USB3 was not enabled during the 
kernel build.

Make sure that CONFIG_USB_XHCI_HCD is enabled.
Or plug the keyboard into a USB2 port if you have one?


I enabled that, along with all of the CONFIG stuff that I could find in 
the BLFS Index of kernel-related software.


See my email of a few minutes ago for details.

A mystery is what exactly fixed the problem. I have both keyboard and 
mouse plugged into USB2 ports on the MB, so I don't see what enabling 
CONFIG_USB_XHCI_HCD could have done.


Thanks!

Alan

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-27 Thread Alan Feuerbacher

Success! I've managed to boot LFS 8.0, X Windows, Firefox and Thunderbird.

I've learned a lot about Linux from this, especially how to boot with an 
EFI bios and GTP partitions.


On 5/25/2017 2:32 PM, Ken Moffat wrote:

On Thu, May 25, 2017 at 12:30:56PM -0600, Alan Feuerbacher wrote:

On 5/25/2017 12:24 PM, Kuba wrote:

On Thu, 25 May 2017 12:19:53 -0600, Alan Feuerbacher
 wrote:


First, may I suggest that sendmail is probably not a mail server
which many people want to use.  It used to be horrendous to
configure.  I run postfix, which provides /usr/sbin/sendmail.


I looked into installing that, but on first glance it looks like a lot 
of work configuring it. Comments?


Now that Thunderbird is working, do I need Postfix?


Just mentioning that in case it is something in sendmail that is
hanging.


Turns out sendmail was working ok. But I've disabled it.


The computer itself quits working -- I have to turn the power switch off and
on to reboot to the host system.


A bit more clarification: Normally when Grub starts, the screen goes 
blank for a few seconds, the mouse and keyboard lights turn off (I have 
an illuminated Logitech keyboard), and after a few seconds it all turns 
back on, and you get the Linux startup messages. In my case, everything 
went blank, and never turned on again. That's why I had to power cycle 
the power supply.



1. My thought process on trying to debug this

With traditional sysvinit, the kernel has invoked init and that has
gone into your chosen runlevel (probably runlevel 3?).  I suggest
that you begin by looking at the bootscript for sendmail, to see if
it starts multiple programs.  If it does, try adding messages
between them.


I looked at several useful bootlog files in /var/log:

boot.log
kern.log
sys.log

These showed that sendmail was working, along with some potential gotchas.


Alternatively, if sendmail really is running ok then the problem
would be with the *next* script (ordered by the SNN symlink
numbers).  But if that next script begins to execute, I would expect
it to report something.  So this sounds to me as if sendmail is not
completing.


I ended up disabling all of the stuff that is started by scripts in 
blfs-bootscripts. The log files indicated no problems except for the NIC 
related stuff, which I eventually sorted out.



If you have enabled MagicSysRQ in your kernel, and your keyboard has
a SysRq key (possibly on PrtScr - labels may differ slightly), you
can probably force a reboot.  For my desktops I think I use AltGr
e(right Alt) and PrintScreen - hit the magic key combination for your
keyboard, followed by s (sync), wait briefly, then use the magic key
combination followed by b (boot) or, at the end of the session o
(off).  These will do unclean shutdowns, so next boot will fsck, but
the Sync will update logs, particularly the system log and maybe the
mail log, boot log (boot log tends to be not very informative).

If you didn't enable that in your kernel config, wait a few minutes
so that the logs have hopefully sync'd.


None of the above could work, since the keyboard and mouse were powered 
off, and the computer hung.



2. Recommendations, now you know how I've got them:

As a first stage, from the host look at the LFS logs to see if there
is anything useful.  If there isn't, as root chmod 644
/mnt/lfs/etc/rc.d/init.d/sendmail so that you can read and edit it
but it will not automatically run.

If you are able to boot without sendmail, you should have a working
keyboard on several ttys : from one of those, root can try starting
sendmail, or just stepping through the invocation(s) in that
bootscript [ i.e. run commands directly ].

Alternatively, and if you have NOT booted this system in LFS before
you added the extra packages, perhaps you did not build the
(correct) keyboard driver (usb and PS/2 might be different, I'm not
sure).


Following the above advice, and that from another email, I did this:

Fixed the various NIC settings (ifconfig, etc.).
Added all of the CONFIG settings I thought were applicable to the Kernel.
Recompiled the kernel.
Disabled all of the blfs-bootscripts startup scripts.

Magically, a reboot worked and I got a login prompt.

Then I reversed all the disabling, one step at a time, and everything 
continued to work.


Finally I installed a bunch more BLFS stuff, X Windows, etc.

Thanks for the help!

Alan

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-26 Thread Wayne Blaszczyk
On Thu, 2017-05-25 at 10:52 -0600, Alan Feuerbacher wrote:
> Since yesterday, I installed quite a bit more BLFS software, plus the 
> rEFInd boot manager from RodsBooks. Sendmail is now installed.
> 
> LFS seems to boot up to the "komodo login:" prompt, and then hangs. 
> Every kernel message shows [ OK ] on the right side of the screen. The 
> last is for "Starting sendmail". The NIC seems to come alive.

I had the same issue and and turned out to be USB3 was not enabled during the 
kernel build.

Make sure that CONFIG_USB_XHCI_HCD is enabled.
Or plug the keyboard into a USB2 port if you have one?

Regards,
Wayne.



> 
> So at this point, I can boot using two methods:
> 
> Grub, which loads vmlinuz-4.9.9-lfs-8.0
> 
> rEFInd, which loads grub, which loads vmlinuz-4.9.9-lfs-8.0
> 
> Each of the two methods results in the same kernel startup messages and 
> then a hang.
> 
> It's as if something is wrong with the vmlinuz image.
> 
> I tried the EFI stub loader method but probably didn't do it properly.
> 
> Ideas?
> 
> Alan
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Michael Shell
On Thu, 25 May 2017 10:52:28 -0600
Alan Feuerbacher  wrote:

> Grub, which loads vmlinuz-4.9.9-lfs-8.0 
> rEFInd, which loads grub, which loads vmlinuz-4.9.9-lfs-8.0 
> Each of the two methods results in the same kernel startup messages and 
> then a hang.


I would try booting directly to a root shell using grub:

https://askubuntu.com/questions/15284/how-to-boot-to-root-shell-when-grub-recovery-menu-fails-to-load-a-shell

linux init=/bin/sh

This way, you should be able to isolate kernel/keyboard problems from
system setup problems.


  Cheers,

  Mike Shell

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Ken Moffat
On Thu, May 25, 2017 at 12:30:56PM -0600, Alan Feuerbacher wrote:
> On 5/25/2017 12:24 PM, Kuba wrote:
> > On Thu, 25 May 2017 12:19:53 -0600, Alan Feuerbacher
> >  wrote:

First, may I suggest that sendmail is probably not a mail server
which many people want to use.  It used to be horrendous to
configure.  I run postfix, which provides /usr/sbin/sendmail.

Just mentioning that in case it is something in sendmail that is
hanging.

> > > 
> > > I would do that if the system were up and running. But as I said, it
> > > hangs up at the login prompt.
> > 
> > How can you be sure it hangs? Maybe, as I said, it's just the keyboard?
> 
> The computer itself quits working -- I have to turn the power switch off and
> on to reboot to the host system.
> 

1. My thought process on trying to debug this

With traditional sysvinit, the kernel has invoked init and that has
gone into your chosen runlevel (probably runlevel 3?).  I suggest
that you begin by looking at the bootscript for sendmail, to see if
it starts multiple programs.  If it does, try adding messages
between them.

Alternatively, if sendmail really is running ok then the problem
would be with the *next* script (ordered by the SNN symlink
numbers).  But if that next script begins to execute, I would expect
it to report something.  So this sounds to me as if sendmail is not
completing.

If you have enabled MagicSysRQ in your kernel, and your keyboard has
a SysRq key (possibly on PrtScr - labels may differ slightly), you
can probably force a reboot.  For my desktops I think I use AltGr
e(right Alt) and PrintScreen - hit the magic key combination for your
keyboard, followed by s (sync), wait briefly, then use the magic key
combination followed by b (boot) or, at the end of the session o
(off).  These will do unclean shutdowns, so next boot will fsck, but
the Sync will update logs, particularly the system log and maybe the
mail log, boot log (boot log tends to be not very informative).

If you didn't enable that in your kernel config, wait a few minutes
so that the logs have hopefully sync'd.

2. Recommendations, now you know how I've got them:

As a first stage, from the host look at the LFS logs to see if there
is anything useful.  If there isn't, as root chmod 644
/mnt/lfs/etc/rc.d/init.d/sendmail so that you can read and edit it
but it will not automatically run.

If you are able to boot without sendmail, you should have a working
keyboard on several ttys : from one of those, root can try starting
sendmail, or just stepping through the invocation(s) in that
bootscript [ i.e. run commands directly ].

Alternatively, and if you have NOT booted this system in LFS before
you added the extra packages, perhaps you did not build the
(correct) keyboard driver (usb and PS/2 might be different, I'm not
sure).

ĸen
-- 
I live in a city. I know sparrows from starlings.  After that
everything is a duck as far as I'm concerned.  -- Monstrous Regiment
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Alan Feuerbacher

On 5/25/2017 12:24 PM, Kuba wrote:

On Thu, 25 May 2017 12:19:53 -0600, Alan Feuerbacher
 wrote:

Try plugging in a thumb drive and see if any messages appear. Be sure
to crank up the logging level tho.


I would do that if the system were up and running. But as I said, it
hangs up at the login prompt.


How can you be sure it hangs? Maybe, as I said, it's just the keyboard?


The computer itself quits working -- I have to turn the power switch off 
and on to reboot to the host system.



Also, I believe you can change the logging level in the kernel config or
parameters.


How do I do that? A "make menuconfig" thing? Do you know what to configure?

Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Kuba
On Thu, 25 May 2017 12:19:53 -0600, Alan Feuerbacher
 wrote:
>> > Try plugging in a thumb drive and see if any messages appear. Be sure
>> > to crank up the logging level tho.
> 
> I would do that if the system were up and running. But as I said, it
> hangs up at the login prompt.

How can you be sure it hangs? Maybe, as I said, it's just the keyboard?
Also, I believe you can change the logging level in the kernel config or
parameters.

> Perhaps there's a way to check apart from a running system? Maybe in
> the chroot build environment?

I'm thinking about a kernel issue, so no.

Kuba
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Alan Feuerbacher

On 5/25/2017 11:59 AM, Kuba wrote:

On Thu, 25 May 2017 11:51:51 -0600, Alan Feuerbacher



Keyboard is USB.

How would I test if the USB subsystem works?


Try plugging in a thumb drive and see if any messages appear. Be sure
to crank up the logging level tho.


I would do that if the system were up and running. But as I said, it 
hangs up at the login prompt.


Perhaps there's a way to check apart from a running system? Maybe in the 
chroot build environment?


Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Kuba
On Thu, 25 May 2017 11:51:51 -0600, Alan Feuerbacher
 wrote:
> This is NOT systemd, but the regular old LFS system. However, I had
> booting issues with a systemd LFS several weeks ago, but I never could
> get past the boot issues. Hence, my latest attempt with non-systemd.

Oh, I thought it was because of some earlier messages mentioning it.

> Keyboard is USB.
> 
> How would I test if the USB subsystem works?

Try plugging in a thumb drive and see if any messages appear. Be sure
to crank up the logging level tho.

Kuba
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Alan Feuerbacher

On 5/25/2017 11:41 AM, Kuba wrote:

On Thu, 25 May 2017 10:52:28 -0600, Alan Feuerbacher
 wrote:

LFS seems to boot up to the "komodo login:" prompt, and then hangs.
Every kernel message shows [ OK ] on the right side of the screen. The
last is for "Starting sendmail". The NIC seems to come alive.


It seems to be a common issue with systemd, possibly while booting by
EFI. Is the keyboard you are using USB or PS/2? Maybe the USB subsystem
in the kernel just doesn't work? Try using a PS/2 keyboard, they're
great for debugging. Apart from that I'm out of ideas since I'm using
the good ol' sysvinit.


This is NOT systemd, but the regular old LFS system. However, I had 
booting issues with a systemd LFS several weeks ago, but I never could 
get past the boot issues. Hence, my latest attempt with non-systemd.


Keyboard is USB.

How would I test if the USB subsystem works?

My new ASUS TUF MB has no PS/2 input. I have a PS/2 keyboard, but I'd 
have to use a PS/2 to USB adapter, which defeats the purpose.


Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Kuba
On Thu, 25 May 2017 10:52:28 -0600, Alan Feuerbacher
 wrote:
> LFS seems to boot up to the "komodo login:" prompt, and then hangs.
> Every kernel message shows [ OK ] on the right side of the screen. The
> last is for "Starting sendmail". The NIC seems to come alive.

It seems to be a common issue with systemd, possibly while booting by
EFI. Is the keyboard you are using USB or PS/2? Maybe the USB subsystem
in the kernel just doesn't work? Try using a PS/2 keyboard, they're
great for debugging. Apart from that I'm out of ideas since I'm using
the good ol' sysvinit.

Kuba
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] Booting from EFI Hints

2017-05-25 Thread Alan Feuerbacher
Since yesterday, I installed quite a bit more BLFS software, plus the 
rEFInd boot manager from RodsBooks. Sendmail is now installed.


LFS seems to boot up to the "komodo login:" prompt, and then hangs. 
Every kernel message shows [ OK ] on the right side of the screen. The 
last is for "Starting sendmail". The NIC seems to come alive.


So at this point, I can boot using two methods:

Grub, which loads vmlinuz-4.9.9-lfs-8.0

rEFInd, which loads grub, which loads vmlinuz-4.9.9-lfs-8.0

Each of the two methods results in the same kernel startup messages and 
then a hang.


It's as if something is wrong with the vmlinuz image.

I tried the EFI stub loader method but probably didn't do it properly.

Ideas?

Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-25 Thread Alan Feuerbacher

On 5/23/2017 4:43 PM, Ken Moffat wrote:
> On Tue, May 23, 2017 at 02:40:03PM -0600, Alan Feuerbacher wrote:
>>
>> However, I'm getting conceptually stuck at how to boot with my EFI
>> motherboard (Asus TUF Mark 1), using the lfs-uefi.txt hint mentioned 
in the

>> LFS book, ch. 8.4.1.

SNIP

>> Two sticking points:
>>
>> 1. I assume that with my present setup, I should use /dev/sdd rather 
than
>> /dev/sda, because I DON'T want to change the Fedora boot stuff. 
Rather, I
>> want to be able to boot directly from the LFS disk. Ultimately, I 
want to

>> use a boot manage like RodsBooks' rEFTnd (which I successfully installed
>> on /dev/sdb). And if I remove all disks, but /dev/sdd, I want to boot
>> directly from that.
>
> I think you are correct.  The hint probably assumes one drive.

So far, I've gone with the assumption to install to /dev/sdd, apparently 
successfully. But see below. Also, I have five disks installed, all 
running and all with different Linuxes in various states, so I have to 
be very careful keeping track of which disk is which.


>> 2. Do I use the LFS book's instructions on partitioning a strictly 
MBR boot

>> setup, or make GPT partitions? See the information and discussion below.
>
> I think you have to use GPT partitions for UEFI.

That's what I've done now.

>> Here is my first cut at /etc/fstab for systemd on /dev/sdc:
>> # file system  mount-point  type options dump  fsck
>> #  order
>>
>> /dev/sdc4 /ext4defaults1 1
>> /dev/sdc3 /bootext4defaults1 2
>> /dev/sdc1 /boot/efivfatdefaults0 2
>> /dev/sdc5 /opt ext4defaults1 2
>> /dev/sdc6 /homeext4defaults1 2
>> /dev/sdc2 swap swappri=1   0 0
>
> I think that looks reasonable.

Ok, here is the new one, after converting to GPT using gdisk:

/dev/sdd4 /ext4defaults1 1
/dev/sdd1 /boot/efivfatdefaults0 1
/dev/sdd3 /bootext4defaults1 2
efivarfs  /sys/firmware/efi/efivars  efivarfs  defaults  01
/dev/sdd5 /opt ext4defaults1 2
/dev/sdd6 /homeext4defaults1 2
/dev/sdd2 swap swappri=1   0 0


> Personally, I long-ago stopped giving /opt its own filesystem:  if
> '/' is big enough, I can rename directories in /opt for testing a
> newer version.

Perhaps this can be included in the discussion of partitioning schemes 
in the LFS book.


>> Question: has anyone on the LFS staff besides the authors (Dan 
McGhee, Kevin

>> M. Buckley) gone through all this? I'm happy to be a guinea pig,
>> because I'm learning a lot.
>
> LOL.  The phrase "staff" used to be used in BLFS - but who is paying
> us ?

Payment is perhaps the satisfaction of a job well done.

I suppose I could have reverted to my Long Island upbringing and said 
"Youse LFS guys".


> I don't know for certain, but I suspect most of the editors
> have been able to disable UEFI on new machines.  My personal opinion
> of UEFI is still "There be dragons."

That's for sure!

On this new machine of mine, I've disabled Secure Boot (had to remove a 
Key) but I'm using UEFI boot, since disabling it means enabling the old 
CSM Legacy boot in the Bios.


> I suspect I might have to learn more about it for my next machine.

I don't think we will have much choice, given that the industry is going 
that way.


I'm thinking that in the long term, I might try installing LFS with 
Secure Boot, ala the material in RodsBooks. The lfs-uefi.txt hint 
mentions this as a good resource.


> No timescale for that, I started using gimp-2.9 on my photo-editing
> machine and discovered it was underpowered (2.9 seemed to only use 1
> core, and the xcf files are a lot bigger) - but meanwhile I'm using
> 2.8 on my development machine and that is ok.  So for me there is no
> rush to get my first ryzen.

Well I had no choice, since my old Windows machine died, and I 
repurposed the old Linux machine for Windows. Meanwhile I bought new 
hardware for Linux, since I'm dumping Windows ASAP.


> I don't think Dan or Kevin have posted on the lists recently, so you
> are probably somewhat on your own.

Ok.

> Being a guinea pig can be fun,
> but less so if hardware gets damaged.  So please think carefully
> about what you are doing at each step (but I imagine the worst thing
> is likely to be a trashed partition, which you can recreate from a
> working system such as fedora).

Already been there. Grub trashed my Fedora boot partition when I used it 
wrongly first time around.



Apparently I messed up sending the above yesterday, so here it is again. 
Sorry if it's a duplicate.


Alan

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscr

Re: [lfs-support] Booting from EFI Hints

2017-05-23 Thread Bruce Dubbs

Ken Moffat wrote:


LOL.  The phrase "staff" used to be used in BLFS - but who is paying
us ?  I don't know for certain, but I suspect most of the editors
have been able to disable UEFI on new machines.  My personal opinion
of UEFI is still "There be dragons."


I agree.  I do not know of any reason to use secure boot or uefi (they are 
separate) unless you want to dual boot to windows.  That's verbotten here.


BTW, I LOLed also at the reference to 'staff'.

  -- Bruce


--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Booting from EFI Hints

2017-05-23 Thread Ken Moffat
On Tue, May 23, 2017 at 02:40:03PM -0600, Alan Feuerbacher wrote:

[ snipping most of the parts I can't reply about ]
> 
> However, I'm getting conceptually stuck at how to boot with my EFI
> motherboard (Asus TUF Mark 1), using the lfs-uefi.txt hint mentioned in the
> LFS
> book, ch. 8.4.1.
> 
> Note that my host Fedora is on /dev/sda, and I'm putting LFS on /dev/sdd.
> Other hard disks contain incomplete experiments, with /dev/sdc containing
> an incomplete systemd.
> 
> >From the lfs-uefi.txt hint in LFS book, ch. 8.4.1 at
> # http://www.linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt
> 
> 
> MOUNT EFI PARTITION
> Determine which device is the EFI partition using gdisk or
> parted,
> enter the chroot environment, create /boot/efi if needed, and
> 
> mount -vt vfat /dev/sda(x) /boot/efi
> 
> where sda(x) is the device containing the EFI partition.
> 
> 
> Two sticking points:
> 
> 1. I assume that with my present setup, I should use /dev/sdd rather than
> /dev/sda, because I DON'T want to change the Fedora boot stuff. Rather, I
> want to be able to boot directly from the LFS disk. Ultimately, I want to
> use a boot manage like RodsBooks' rEFTnd (which I successfully installed
> on /dev/sdb). And if I remove all disks, but /dev/sdd, I want to boot
> directly from that.

I think you are correct.  The hint probably assumes one drive.
> 
> 2. Do I use the LFS book's instructions on partitioning a strictly MBR boot
> setup, or make GPT partitions? See the information and discussion below.
> 

I think you have to use GPT partitions for UEFI.
> filesystem
>6   908072960  1953525134   498.5 GiB   8300  Linux
> filesystem
> ##
> 
> Here is my first cut at /etc/fstab for systemd on /dev/sdc:
> ##
> [root@localhost rootlfs1]# cat etc/fstab
> # Begin /etc/fstab
> 
> # file system  mount-point  type options dump  fsck
> #  order
> 
> /dev/sdc4 /ext4defaults1 1
> /dev/sdc3 /bootext4defaults1 2
> /dev/sdc1 /boot/efivfatdefaults0 2
> /dev/sdc5 /opt ext4defaults1 2
> /dev/sdc6 /homeext4defaults1 2
> /dev/sdc2 swap swappri=1   0 0
> ##
> 

I think that looks reasonable.  If you ever want to use that to
build a newer / second-attempt LFS on the same disk, you will also
need a spare partition for the new system.

Personally, I long-ago stopped giving /opt its own filesystem:  if
'/' is big enough, I can rename directories in /opt for testing a
newer version.
> ##
> 
> Given the above and the discussion of having a /boot/efi vfat partition
> in the
> hints, I'm thinking that the /dev/sdd fstab should be this:
> 
> ##
> ...
> /dev/sdd5  /ext4 defaults1 1
> /dev/sdd3  /bootext4 defaults1 2
> /dev/sdd1  /boot/efivfat defaults0 2
> /dev/sdd6  /opt ext4 defaults1 2
> /dev/sdd7  /homeext4 defaults1 2
> /dev/sdd2  swap swap pri=1   0 0
> ...
> ##
> Note that /dev/sdd4 would be the MBR extended partition.

No, forget about MBR.  GPT is the way to go on recent machines, it
allows many partitions.
> 
> While I wait for some advice, I'll be installing the extra software required
> by the hints.
> 
> Question: has anyone on the LFS staff besides the authors (Dan McGhee, Kevin
> M. Buckley) gone through all this? I'm happy to be a guinea pig,
> because I'm learning a lot.
> 
> Alan
> 

LOL.  The phrase "staff" used to be used in BLFS - but who is paying
us ?  I don't know for certain, but I suspect most of the editors
have been able to disable UEFI on new machines.  My personal opinion
of UEFI is still "There be dragons."

I suspect I might have to learn more about it for my next machine.
No timescale for that, I started using gimp-2.9 on my photo-editing
machine and discovered it was underpowered (2.9 seemed to only use 1
core, and the xcf files are a lot bigger) - but meanwhile I'm using
2.8 on my development machine and that is ok.  So for me there is no
rush to get my first ryzen.

I don't think Dan or Kevin have posted on the lists recently, so you
are probably somewhat on your own.  Being a guinea pig can be fun,
but less so if hardware gets damaged.  So please think carefully
about what you are doing at each step (but I imagine the worst thing
is likely to be a trashed partition, which you can recreate from a
working system such as fedora).

ĸen
-- 
I live in a city. I know sparrows from starlings.  After that
everything is a duck as far as I'm concerned.  -- Monstrous Regiment
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe

[lfs-support] Booting from EFI Hints

2017-05-23 Thread Alan Feuerbacher
Following the advice of akhiezer in his note from 18-May-2017, I'm going 
back to try to install LFS stable version 8.0, in order to gradually work
up to installing LFS systemd development version with LVM, LABEL/UUID in 
fstab, intramfs, etc.


However, I'm getting conceptually stuck at how to boot with my EFI 
motherboard (Asus TUF Mark 1), using the lfs-uefi.txt hint mentioned in 
the LFS

book, ch. 8.4.1.

Note that my host Fedora is on /dev/sda, and I'm putting LFS on 
/dev/sdd. Other hard disks contain incomplete experiments, with /dev/sdc 
containing

an incomplete systemd.

>From the lfs-uefi.txt hint in LFS book, ch. 8.4.1 at
# http://www.linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt


MOUNT EFI PARTITION
Determine which device is the EFI partition using gdisk or
parted,
enter the chroot environment, create /boot/efi if needed, and

mount -vt vfat /dev/sda(x) /boot/efi

where sda(x) is the device containing the EFI partition.


Two sticking points:

1. I assume that with my present setup, I should use /dev/sdd rather 
than /dev/sda, because I DON'T want to change the Fedora boot stuff. 
Rather, I
want to be able to boot directly from the LFS disk. Ultimately, I want 
to use a boot manage like RodsBooks' rEFTnd (which I successfully installed
on /dev/sdb). And if I remove all disks, but /dev/sdd, I want to boot 
directly from that.


2. Do I use the LFS book's instructions on partitioning a strictly MBR 
boot setup, or make GPT partitions? See the information and discussion 
below.


To let you see my setup, I've gotten some info on my setup from various 
disk commands.


The difference between a stricly MBR partition scheme and a GPT scheme 
can be seen in the outputs from the following info commands, executed in the
LFS chroot or Fedora host environment as needed. Note that I'm inserting 
some comments for clarification:


# In LFS chroot:
##
root:/sources# lsblk
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
...
# Development Version 20170518-systemd
sdc 8:32   0   1.8T  0 disk
|-sdc1  8:33   0 1G  0 part
|-sdc2  8:34   032G  0 part
|-sdc3  8:35   0 1G  0 part
|-sdc4  8:36   0   200G  0 part
|-sdc5  8:37   0   200G  0 part
`-sdc6  8:38   0   500G  0 part
# Stable Version 8.0
sdd 8:48   0 931.5G  0 disk
|-sdd1  8:49   0 1G  0 part /boot
|-sdd2  8:50   032G  0 part [SWAP]
|-sdd3  8:51   0   200G  0 part /
|-sdd4  8:52   0 1K  0 part
|-sdd5  8:53   0   200G  0 part /opt
`-sdd6  8:54   0 498.5G  0 part /home
...
##

# In LFS chroot:
##
root:/sources# fdisk -l /dev/sdc
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 758C423C-3C5D-472B-92C3-ACB1B2026A7A

Device StartEndSectors  Size Type
/dev/sdc1   2048209919920971521G EFI System
/dev/sdc22099200   69208063   67108864   32G Linux swap
/dev/sdc3   69208064   7130521520971521G Linux filesystem
/dev/sdc4   71305216  490735615  419430400  200G Linux filesystem
/dev/sdc5  490735616  910166015  419430400  200G Linux filesystem
/dev/sdc6  910166016 1958742015 1048576000  500G Linux filesystem
##

##
root:/sources# fdisk -l /dev/sdd
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x66f87996

Device Boot StartEndSectors   Size Id Type
/dev/sdd1  * 204820991992097152 1G 83 Linux
/dev/sdd2 2099200   69208063   6710886432G 82 Linux swap /
Solaris
/dev/sdd369208064  488638463  419430400   200G 83 Linux
/dev/sdd4   488638464 1953525167 1464886704 698.5G  5 Extended
/dev/sdd5   488640512  908070911  419430400   200G 83 Linux
/dev/sdd6   908072960 1953525134 1045452175 498.5G 83 Linux
##

# On Fedora host:
##
[root@localhost alan]# gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 758C423C-3C5D-472B-92C3-ACB1B2026A7A
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 1948289133 sectors (929.0 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   1