dhull wrote:
> Paul,
>
> I've tested installing Samba by installing it at the end of a clean
> install from scratch. I have convinced myself that the Set Samba dialog
> with Samba running and a new password in the field does NOT create a
> Samba user. Invoking the command "sudo pdbedit -L"
Starting from the new kernel ( 4.9.x ) in Picoreplayer 3.20 Beta the
great work of Hias has started become available to people who like the
simplicity and stability of running PCP as basis to squeezelite.
The mentioned Pi audio card is one of the most advanced cards with great
specs, that do go
paul- wrote:
> Nothing was changed with samba in 3.20 from 3.11. You have always had
> to set the password from the web interface.. this adds a user and
> password.
>
> usr/local/var/lib/samba is already added to the backup set. That takes
> care of everything recursively below.
Paul,
paul- wrote:
> There does appear to be a timing issue when the drivers are loaded, vs
> when the modprobe.conf file is updated at boot time.I'm really not
> sure where to go here without hardware in my hands to work out the bugs.
Hi Paul, Indeed finding the bug is difficult without direct
efthk23 wrote:
> Thx for your quick reply. I've done everything you suggested but the
> white screen is still there. when i type the dmesg command, it returns
> this many times: status 0x8001
> [ 351.495198] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer
> (-22)
> [ 351.495204]
Thx for your quick reply. I've done everything you suggested but the
white screen is still there. when i type the dmesg command, it returns
this many times: status 0x8001
[ 351.495198] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer
(-22)
[ 351.495204] bcm2708_fb_pan_display(0,0)
Wifi drivers are for the most part controlled by the upstream kernel,
there are a few exceptions. I've seen many drivers break due to
upstream changes. The rtl8192cu driver is one that has been a
nightmare. With that driver, we decided to follow what OSMC does and
revert to an older 8192cu
mherger wrote:
> > I tried replacing the framework call with the os shutdown but
> couldn't
> > make it work.
> > The command is not executed, you just get the screen bump.
>
> "sudo: shutdown: command not found" :-)
>
> Use "halt" instead and it works as expected.
>
> --
>
> Michael
Guess
