Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #197286 > unrolled thread

Editing a piped in stream?

Back to article view | Back to linux.debian.user

Contents

  Editing a piped in stream? Richard Owlett <rowlett@cloud85.net> - 2018-07-06 18:20 +0200
    Re: Editing a piped in stream? Michael Wagner <wagner_m_bremen@web.de> - 2018-07-06 18:50 +0200
      Re: Editing a piped in stream? Richard Owlett <rowlett@cloud85.net> - 2018-07-06 20:30 +0200
    Re: Editing a piped in stream? john doe <johndoe65534@mail.com> - 2018-07-06 19:10 +0200
    Re: Editing a piped in stream? David Christensen <dpchrist@holgerdanske.com> - 2018-07-07 04:10 +0200
      Re: Editing a piped in stream? John Crawley <john@bunsenlabs.org> - 2018-07-07 11:00 +0200
        Re: Editing a piped in stream? David Christensen <dpchrist@holgerdanske.com> - 2018-07-07 21:40 +0200
          Re: Editing a piped in stream? David Wright <deblis@lionunicorn.co.uk> - 2018-07-08 03:40 +0200
            Eureka;/ Re: Editing a piped in stream? Richard Owlett <rowlett@cloud85.net> - 2018-07-08 13:00 +0200
          Re: Editing a piped in stream? John Crawley <john@bunsenlabs.org> - 2018-07-08 03:40 +0200
            Re: Editing a piped in stream? john doe <johndoe65534@mail.com> - 2018-07-08 07:40 +0200
              Re: Editing a piped in stream? Andy Smith <andy@strugglers.net> - 2018-07-08 13:20 +0200
                Re: Editing a piped in stream? Richard Owlett <rowlett@cloud85.net> - 2018-07-08 15:20 +0200
                  Re: Editing a piped in stream? Richard Owlett <rowlett@cloud85.net> - 2018-07-08 16:00 +0200
                    Re: Editing a piped in stream? John Darrah <xyllyx@gmail.com> - 2018-07-08 18:50 +0200
                      Re: Editing a piped in stream? mick crane <mick.crane@gmail.com> - 2018-07-10 14:20 +0200
                        Re: Editing a piped in stream? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-10 14:40 +0200
                          Re: Editing a piped in stream? mick crane <mick.crane@gmail.com> - 2018-07-10 15:00 +0200
                        Re: Editing a piped in stream? john doe <johndoe65534@mail.com> - 2018-07-10 15:30 +0200
                Re: Editing a piped in stream? mick crane <mick.crane@gmail.com> - 2018-07-10 14:50 +0200
              Re: Editing a piped in stream? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-09 14:50 +0200
                Re: Nvidia drivers Matthew Crews <mattcrews@mattcrews.com> - 2018-07-09 15:20 +0200
                  Re: Nvidia drivers Matthew Crews <mattcrews@mattcrews.com> - 2018-07-09 20:40 +0200
                    Re: Nvidia drivers Boyan Penkov <boyan.penkov@gmail.com> - 2018-07-09 20:50 +0200

Page 2 of 2 — ← Prev page 1 [2]

#197390

On Sun, Jul 08, 2018 at 07:39:07AM +0200, john doe wrote:
> The issue here is that we don't know what the OP wants (original and desired
> output)!!! :)

Indeed.  That's nearly always the problem (not just with this individual).

https://mywiki.wooledge.org/XyProblem
https://mywiki.wooledge.org/ParsingLs

[toc] | [prev] | [next] | [standalone]

#197393 — Re: Nvidia drivers

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote:
>> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote:
>>     This requires a workaround, a kernel parameter at boot.
>>     GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y"
>>     Edit the config file like this,
>>     $sudo gedit /etc/default/grub
>>     Then run $sudo update-grub.
> Actually, as of version 390.67-2, that's no longer needed. Quoting [1]:

I just tested with 4.16 kernel and 390.67-2 nvidia-driver, and
unfortunately this work-around is still required on my system. I was
unable to boot my system properly without the kernel parameter in GRUB.

[toc] | [prev] | [next] | [standalone]

#197408 — Re: Nvidia drivers

On 7/9/18 5:55 AM, Matthew Crews wrote:
> On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote:
>>> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote:
>>>     This requires a workaround, a kernel parameter at boot.
>>>     GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y"
>>>     Edit the config file like this,
>>>     $sudo gedit /etc/default/grub
>>>     Then run $sudo update-grub.
>> Actually, as of version 390.67-2, that's no longer needed. Quoting [1]:
> 
> I just tested with 4.16 kernel and 390.67-2 nvidia-driver, and
> unfortunately this work-around is still required on my system. I was
> unable to boot my system properly without the kernel parameter in GRUB.
> 

You know what? Thats actually not true. I didn't realize that I was
still using the old driver version when I tested.

🤦‍♂️

You can disregard. The kernel parameter is not needed with 390.67-2

[toc] | [prev] | [next] | [standalone]

#197409 — Re: Nvidia drivers

[Multipart message — attachments visible in raw view] — view raw

Thanks for being a good guy and following up; I was looking into this 
and this report was keeping me from apt-get dist-upgrade this evening, 
so I know I'm OK now...

Silent thanks to all that have faffed with getting this sorted in the 
last week -- cheers!

On 07/09/2018 02:17 PM, Matthew Crews wrote:
> On 7/9/18 5:55 AM, Matthew Crews wrote:
>> On Fri, Jul 06, 2018 at 09:55:45AM +0100, Darac Marjal wrote:
>>>> On Thu, Jul 05, 2018 at 08:03:22PM -0500, Mark Allums wrote:
>>>>      This requires a workaround, a kernel parameter at boot.
>>>>      GRUB_CMDLINE_LINUX_DEFAULT="slab_common.usercopy_fallback=y"
>>>>      Edit the config file like this,
>>>>      $sudo gedit /etc/default/grub
>>>>      Then run $sudo update-grub.
>>> Actually, as of version 390.67-2, that's no longer needed. Quoting [1]:
>> I just tested with 4.16 kernel and 390.67-2 nvidia-driver, and
>> unfortunately this work-around is still required on my system. I was
>> unable to boot my system properly without the kernel parameter in GRUB.
>>
> You know what? Thats actually not true. I didn't realize that I was
> still using the old driver version when I tested.
>
> 🤦‍♂️
>
> You can disregard. The kernel parameter is not needed with 390.67-2
>
>

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web