I
meant 'general form', you interpreted 'identical'. But it will start
with the linux16 /vmlinuz
The idea is that it will show if there are any unusual kernel options on
that line that might be causing your problem. And if it has quiet on it
that would explain why you aren'
On Thu, 23 Aug 2018 13:44:40 -0700, stan wrote:
> [] I mean the lines in
> the actual grub.cfg file in /boot. That file will be in /boot/grub2,
> or /boot/efi/EFI/fedora/grub.cfg, depending on whether you are using
> bios boot or efi boot.
>
> What I mean will look something like this:
>
>
On Wed, 22 Aug 2018 15:41:54 + (UTC)
Beartooth wrote:
> On Sun, 19 Aug 2018 10:15:15 -0700, stan wrote:
>
> > Can you post your boot command line?
>
> In /etc/default/grub I see
> GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/ root rd.lvm.lv=fedora/swap
> quiet" (all one line). Is that w
Beartooth writes:
> In /etc/default/grub I see GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/ root
> rd.lvm.lv=fedora/swap quiet" (all one line). Is that what you mean??
Don't know if my messages are getting through, because I already sent a
one related to this. If you have tried this, then ignore freely
On Sun, 19 Aug 2018 10:15:15 -0700, stan wrote:
> On Sun, 19 Aug 2018 16:24:49 + (UTC)
> Beartooth wrote:
>
>> On Sun, 19 Aug 2018 13:08:16 +0300, Jarmo Hurri wrote:
>>
>> >> On Fri, 17 Aug 2018 15:30:41 -0700, Samuel Sieb wrote:
>>
>> >>> Does taking out "rhgb" from the boot command line
Beartooth writes:
Does taking out "rhgb" from the boot command line do what you want?
>>>
>>> It doesn't seem to.
>>
>> Try removing "rhgb" and "quiet". The following Ansible rule [...]
>
> Still no joy on either non-GUI PC
That is weird.
> I don't have Ansible installed (and fr
On Sun, 19 Aug 2018 16:24:49 + (UTC)
Beartooth wrote:
> On Sun, 19 Aug 2018 13:08:16 +0300, Jarmo Hurri wrote:
>
> >> On Fri, 17 Aug 2018 15:30:41 -0700, Samuel Sieb wrote:
>
> >>> Does taking out "rhgb" from the boot command line do what you
> >>> want?
> >>
> >>It doesn't seem to
On Sun, 19 Aug 2018 13:08:16 +0300, Jarmo Hurri wrote:
>> On Fri, 17 Aug 2018 15:30:41 -0700, Samuel Sieb wrote:
>>> Does taking out "rhgb" from the boot command line do what you want?
>>
>> It doesn't seem to.
>
> Try removing "rhgb" and "quiet". The following Ansible rule [...]
Jarmo Hurri writes:
>> On Fri, 17 Aug 2018 15:30:41 -0700, Samuel Sieb wrote:
>>
>>> On 08/17/2018 12:57 PM, Beartooth wrote:
>>>>Is there a way to tell plymouth to default to showing boot
>>>> messages?
>>>
>>> Doe
> On Fri, 17 Aug 2018 15:30:41 -0700, Samuel Sieb wrote:
>
>> On 08/17/2018 12:57 PM, Beartooth wrote:
>>> Is there a way to tell plymouth to default to showing boot
>>> messages?
>>
>> Does taking out "rhgb" from the boot command line
On Fri, 17 Aug 2018 15:30:41 -0700, Samuel Sieb wrote:
> On 08/17/2018 12:57 PM, Beartooth wrote:
>> Is there a way to tell plymouth to default to showing boot
>> messages?
>
> Does taking out "rhgb" from the boot command line do what you want?
It
On 08/17/2018 12:57 PM, Beartooth wrote:
Is there a way to tell plymouth to default to showing boot
messages?
Does taking out "rhgb" from the boot command line do what you want?
___
users mailing list -- users@lists.fedoraproj
Is there a way to tell plymouth to default to showing boot
messages?
--
Beartooth Implacable, Erstwhile Historian of Tongues
Who shall gather the smoke of the dead wood burning,
Or behold the flowing years from the Sea returning?
-- JRR Tolkien
On 08/09/2017 07:59 AM, mitchell@member.fsf.org wrote:
> Rick Stevens writes:
>
>>
>>
>> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
>> /lib64/ld-linux-x86-64.so.2
>> /boof
>> /dev
>> /boot/grub/menu.lst
>> /etc/grub2-efi.cfg
>> /boot/grub/grub.cfg
>> /etc/grub.d/
>> /boot/
Rick Stevens writes:
>
>
> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
> /lib64/ld-linux-x86-64.so.2
> /boof
> /dev
> /boot/grub/menu.lst
> /etc/grub2-efi.cfg
> /boot/grub/grub.cfg
> /etc/grub.d/
> /boot/grub2/grubenv
> /etc/mtab
> /boot
> /etc/sysconfig/grub
> /proc/mdstat
>
On 8 August 2017 at 20:59, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
>
>> Note that on your next kernel upgrade, however, the "rhgb quiet" will
>> reappear unless you edit the /etc/default/grub file and those bits from
>> the "GRUB_CMDLINE_LINUX" variable in ther
On 08/08/2017 12:26 PM, Bob Goodwin wrote:
> On 08/08/17 14:50, Rick Stevens wrote:
>> So, yes, you're using UEFI to boot. All you need to do is edit the
>> /boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
>> reboot. You should be fine.
>>
>> Note that on your next kernel upgr
On 08/08/17 14:50, Rick Stevens wrote:
So, yes, you're using UEFI to boot. All you need to do is edit the
/boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
reboot. You should be fine.
Note that on your next kernel upgrade, however, the "rhgb quiet" will
reappear unless you e
On 08/08/2017 11:59 AM, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
>
>> Note that on your next kernel upgrade, however, the "rhgb quiet" will
>> reappear unless you edit the /etc/default/grub file and those bits from
>> the "GRUB_CMDLINE_LINUX" variable in there a
On Tue, 8 Aug 2017 11:50:54 -0700
Rick Stevens wrote:
> Note that on your next kernel upgrade, however, the "rhgb quiet" will
> reappear unless you edit the /etc/default/grub file and those bits from
> the "GRUB_CMDLINE_LINUX" variable in there as well.
That hasn't been my experience. The "grubby
On 08/08/2017 11:24 AM, Bob Goodwin wrote:
> On 08/08/17 14:02, Rick Stevens wrote:
>>> I see two boot partitions:
>>>
>>> /dev/sda2 976M 167M 742M 19% /boot
>>> /dev/sda1 200M 9.5M 191M 5% /boot/efi
>>>
>>> But it says "efi" not "uefi" and I dunno what the difference is.
>
On 08/08/17 14:02, Rick Stevens wrote:
I see two boot partitions:
/dev/sda2 976M 167M 742M 19% /boot
/dev/sda1 200M 9.5M 191M 5% /boot/efi
But it says "efi" not "uefi" and I dunno what the difference is.
There really isn't. "efi" and "uefi" are synonymous in this conte
On 08/08/2017 10:24 AM, Bob Goodwin wrote:
> On 08/08/17 13:10, Tom Horsley wrote:
>> (The main problem being finding
>> the grub.cfg file if you have a uefi system - it is hidden
>> pretty well :-).
>
> +
>
> Then that must be my problem?
>
> I see two boot partitions:
>
> dev/sda2
On 08/08/17 13:10, Tom Horsley wrote:
(The main problem being finding
the grub.cfg file if you have a uefi system - it is hidden
pretty well :-).
+
Then that must be my problem?
I see two boot partitions:
dev/sda2 976M 167M 742M 19% /boot
/dev/sda1 200M 9.5M 191M 5
On Tue, 8 Aug 2017 13:03:46 -0400
Bob Goodwin wrote:
> Obviously this is wrong? Whay should I be doing or is this something I
> can no longer change?
Nothing ever looks at /etc/default/grub or runs grub2-mkconfig unless
you manually run it.
I just edit the grub.cfg file itself. It works perfect
I prefer not watching the blank screen with the egg turning into an F
and normally remove rhgb from /etc/default/grub.
That is not having the desired effect on this Fedora-26 system.
[root@Box10 bobg]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux ima
On 10/08/2016 01:48 PM, François Patte wrote:
At the early beginning of the boot sequence, I have these kinds of messages:
nouveau :01:00.0 outp 04.0006:0344 no bios dp data
What do they mean? Is there something to change in the bios
configuration to satisfy f24?
Is there a problem? I wou
Bonjour,
At the early beginning of the boot sequence, I have these kinds of messages:
nouveau :01:00.0 outp 04.0006:0344 no bios dp data
What do they mean? Is there something to change in the bios
configuration to satisfy f24?
Thank you.
--
François Patte
UFR de mathématiques et informati
On 03.10.2016 15:35, François Patte wrote:
> Bonjour,
>
> I am wondering why since f23 the boot messages display stops at "switch
> root"?
>
> on f21 all thee messages are displayed...
>
> Thank you.
>
> --
> François Patte
> UFR de mathéma
Bonjour,
I am wondering why since f23 the boot messages display stops at "switch
root"?
on f21 all thee messages are displayed...
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-7
On Mon, 11 Nov 2013 20:01:29 -0500
Robert McBroom wrote:
> While starting my system I get the following messages. What is
> happening? Up to date Fedora 19
I don't know for sure, but "hal" was declared dead a while
back (I think maybe it was blown up in orbit around europa :-).
Anything talki
While starting my system I get the following messages. What is
happening? Up to date Fedora 19
[ 11.835466] systemd[1]: Unit iscsid.service entered failed state.
[ 14.019245] systemd-udevd[991]: failed to execute
'/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event'
'socket:@/org/freed
On 24/11/11 18:27, Chris Adams wrote:
> Once upon a time, Morgan Read said:
>> Thanks for getting back - I followed your instructions. It seemed I
>> needed to swap console=ttyS0 and console=tty0 BUT opposite from what you
>> suggested. That is, console=ttyS0 was last and by swapping it with
>>
Once upon a time, Morgan Read said:
> Thanks for getting back - I followed your instructions. It seemed I
> needed to swap console=ttyS0 and console=tty0 BUT opposite from what you
> suggested. That is, console=ttyS0 was last and by swapping it with
> console=tty0 and making console=ttyS0 listed
prompt - but, between the grub menu and the login
>> prompt I'm missing the boot messages. If I remove "quiet" from
>> grub.conf's kernel line I get kernel messages reported to ttyS0, but
>> leaving "quiet" in boot messages are report to tty0 but not ttyS0.
On Sat, Nov 19, 2011 at 7:19 PM, Morgan Read wrote:
> Hello Folks
>
> I'm running f14 (still)
>
> I've successfully configured my machine (hp ml150 g3) to redirect bios,
> grub menu and login prompt - but, between the grub menu and the login
> prompt I'm mis
Hello Folks
I'm running f14 (still)
I've successfully configured my machine (hp ml150 g3) to redirect bios,
grub menu and login prompt - but, between the grub menu and the login
prompt I'm missing the boot messages. If I remove "quiet" from
grub.conf's kernel line
On Mon, Dec 13, 2010 at 3:34 AM, Tim wrote:
>> Detective work. Two commands that help are lsusb and lspci.
>
> Seeing as I recall the original poster mentioning that there were a new
> Linux user, these might be a handy hints:
>
One more addition with regards to this, the OP might be overwhelmed
On Sun, 2010-12-12 at 08:45 -0700, stan wrote:
> Detective work. Two commands that help are lsusb and lspci.
Seeing as I recall the original poster mentioning that there were a new
Linux user, these might be a handy hints:
"ls" is the command used to list files and directories on Linux.
"lsusb"
help are lsusb and lspci. Also,
look in /var/log/messages. All the boot messages are stored there and
these sometimes indicate what is causing the problem. Search the web
for something like linux troubleshooting or boot error messages and
read the collective wisdom. :-)
> How do I submit a bug
On Sun, 2010-12-12 at 09:54 +1300, Fred Zinsli wrote:
> Thanks for the comment, although it has raised more questions for me.
>
> I haven't added any new hardware, unless you count the fact that I did
> connect my new phone to charge it. and I connected my USB bluetooth dongle
> to transfer data t
> "Fred Zinsli" wrote:
>
>> I note there is a boot messages alert. Below is a short piece of that
>> message.
>>
>> I don't have a clue what they mean or how to fix it.
>>
>> Any comments would be most helpful.
>
>> Boot Messages:
&
On Sun, 12 Dec 2010 06:43:34 +1300 (NZDT)
"Fred Zinsli" wrote:
> I note there is a boot messages alert. Below is a short piece of that
> message.
>
> I don't have a clue what they mean or how to fix it.
>
> Any comments would be most helpful.
> Boot
the login screen.
I note there is a boot messages alert. Below is a short piece of that
message.
I don't have a clue what they mean or how to fix it.
Any comments would be most helpful.
Regards
Fred
Boot Messages:
ION match 'add'(plain)
udevd-work[460]: M ATTRS match 'id
I am getting the following boot messages:-
WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d/
System seems to work OK, what should I be doing about
Simon Tierney conditional-fee.co.uk> writes:
>
> I am getting the following boot messages:-
>
> WARNING: Deprecated config file /etc/modprobe.conf, all config files
> belong into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config file
On Thu, 2010-07-15 at 00:55 -0500, Christofer C. Bell wrote:
> On Wed, Jul 14, 2010 at 10:07 PM, Robert G. (Doc) Savage
> wrote:
> >
> > On Fri, 2010-07-09 at 20:58 +, BeartoothHOS wrote:
> >> Several machines have been showing lines like these :
> >>
> >> Press 'I' to en
On 07/15/2010 01:55 AM, Christofer C. Bell wrote:
> On Wed, Jul 14, 2010 at 10:07 PM, Robert G. (Doc) Savage
> wrote:
>
>> On Fri, 2010-07-09 at 20:58 +, BeartoothHOS wrote:
>>
>>> Several machines have been showing lines like these :
>>>
>>> Press 'I' to enter in
On 07/15/2010 01:55 AM, Christofer C. Bell wrote:
> On Wed, Jul 14, 2010 at 10:07 PM, Robert G. (Doc) Savage
> wrote:
>
>> On Fri, 2010-07-09 at 20:58 +, BeartoothHOS wrote:
>>
>>> Several machines have been showing lines like these :
>>>
>>> Press 'I' to enter in
On Wed, Jul 14, 2010 at 10:07 PM, Robert G. (Doc) Savage
wrote:
>
> On Fri, 2010-07-09 at 20:58 +, BeartoothHOS wrote:
>> Several machines have been showing lines like these :
>>
>> Press 'I' to enter interactive startup.
>> Starting udev: udevd[405]: BUS= will be removed
On Fri, 2010-07-09 at 20:58 +, BeartoothHOS wrote:
> Several machines have been showing lines like these :
>
> Press 'I' to enter interactive startup.
> Starting udev: udevd[405]: BUS= will be removed in a future udev version,
> please use SUBSYSTEM= to match the event
On 07/09/2010 01:58 PM, BeartoothHOS wrote:
> Several machines have been showing lines like these :
>
> Press 'I' to enter interactive startup.
> Starting udev: udevd[405]: BUS= will be removed in a future udev version,
> please use SUBSYSTEM= to match the event device, or
Several machines have been showing lines like these :
Press 'I' to enter interactive startup.
Starting udev: udevd[405]: BUS= will be removed in a future udev version,
please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match
a parent device, in /etc/udev
53 matches
Mail list logo
