Florian Zieboll writes:
> Rainer Weikusat wrote:
>
>
>> JFTR: The point of the [] in
>>
>> ps faux | grep get[t]y
>>
>> was that it eliminates the grep itself from the output.
>
>
> Would you please elaborate on this magic?! I found a great RegEx
> reference (1) by the way, but no answer, I'm s
On 03/07/2016 06:46 PM, fsmithred wrote:
Have you tried adding 'nomodeset' to the boot command? Which nvidia card
are you using?
This seems to have fixed it. Oddly enough, another devuan box I have
does not need this boot param. hrm... I took it one step further and
rebooted with "vga=791"
Didier Kryn writes:
> Le 08/03/2016 17:32, dev a écrit :
>>
>> $ ls -l /dev/tty[1-6]
>> crw--w 1 root tty 4, 1 Mar 8 08:08 /dev/tty1
>> crw--w 1 root tty 4, 2 Mar 8 10:09 /dev/tty2
>> crw--w 1 root tty 4, 3 Mar 8 08:08 /dev/tty3
>> crw--w 1 root tty 4, 4 Mar 8 08:08 /dev/tty4
>
On Tue, 08 Mar 2016 16:45:59 +
Rainer Weikusat wrote:
> JFTR: The point of the [] in
>
> ps faux | grep get[t]y
>
> was that it eliminates the grep itself from the output.
Would you please elaborate on this magic?! I found a great RegEx
reference (1) by the way, but no answer, I'm stunne
Le 08/03/2016 17:32, dev a écrit :
$ ls -l /dev/tty[1-6]
crw--w 1 root tty 4, 1 Mar 8 08:08 /dev/tty1
crw--w 1 root tty 4, 2 Mar 8 10:09 /dev/tty2
crw--w 1 root tty 4, 3 Mar 8 08:08 /dev/tty3
crw--w 1 root tty 4, 4 Mar 8 08:08 /dev/tty4
crw--w 1 root tty 4, 5 Mar 8 08:08
dev writes:
> On 03/07/2016 11:28 AM, Steve Litt wrote:
> :: Step 1 is this:
> ::
> :: ps ax | grep getty
>
>
> Thanks Steve. Mine is:
>
> $ ps ax | grep getty
> 2575 tty1 Ss+0:00 /sbin/getty 38400 tty1
> 2576 tty2 Ss+0:00 /sbin/getty 38400 tty2
> 2577 tty3 Ss+0:00 /sbi
On 03/07/2016 11:28 AM, Steve Litt wrote:
:: Step 1 is this:
::
:: ps ax | grep getty
Thanks Steve. Mine is:
$ ps ax | grep getty
2575 tty1 Ss+0:00 /sbin/getty 38400 tty1
2576 tty2 Ss+0:00 /sbin/getty 38400 tty2
2577 tty3 Ss+0:00 /sbin/getty 38400 tty3
2578 tty4
On 03/07/2016 09:40 AM, dev wrote:
Hello,
I noticed today, upon trying to rebuild my nvidia module, that I have no
login available on the virtual terminals customarily available via the
keypress [CTRL][ALT]+(F1-F8 keys).
And this is /proc/cmdline. Nothing odd in there either:
BOOT_IMAGE=/
On Mon, Mar 07, 2016 at 12:28:12PM -0500, Steve Litt wrote:
> On Mon, 7 Mar 2016 08:40:02 -0600
> dev wrote:
>
> > Hello,
> > I noticed today, upon trying to rebuild my nvidia module, that I have
> > no login available on the virtual terminals customarily available via
> > the keypress [CTRL][ALT
On Mon, 7 Mar 2016 08:40:02 -0600
dev wrote:
> Hello,
> I noticed today, upon trying to rebuild my nvidia module, that I have
> no login available on the virtual terminals customarily available via
> the keypress [CTRL][ALT]+(F1-F8 keys).
>
> The keypresses work, showing console output, but ther
dev writes:
> Hello,
> I noticed today, upon trying to rebuild my nvidia module, that I have
> no login available on the virtual terminals customarily available via
> the keypress [CTRL][ALT]+(F1-F8 keys).
>
> The keypresses work, showing console output, but there is no "login:"
>
> /etc/inittab i
Hello,
I noticed today, upon trying to rebuild my nvidia module, that I have no
login available on the virtual terminals customarily available via the
keypress [CTRL][ALT]+(F1-F8 keys).
The keypresses work, showing console output, but there is no "login:"
/etc/inittab is here:
$ egrep -v '(#
12 matches
Mail list logo