Discussion, talk and tips
https://forum.puppylinux.com/
As puppy is by default member of group wheel (check if it really is):
Add to /etc/sudoers:
%wheel ALL=(ALL) NOPASSWD: ALL
Or even better, add the same to the file /etc/sudoers.d/user_wheel (should also exist by default).
Thanks. I'm going to spend a little time using it logged in as puppy and make some .desktop files, write some little scripts, etc to make using it as puppy a less pia experience, which hopefully you can include with the mklive script.
I haven't reported it before because I had a kind of weird Bullseye setup on my laptop and I can't really reproduce it, but I'm getting it now in Bookworm too, both conventional setup and experiments with systemd and pipewire. A search through var/logs/messages for wlan0 doesn't show any obvious failure.
About 20% of the time the wireless fails to connect on reboot. It doesn't see wlan0 and restarting Peasywifi doesn't help. I have to reboot to get it to load. Once it boots correctly, it works fine from then on.
It feels like a race condition where the wireless driver doesn't get loaded sometimes.
Is there someplace I can add some wait time to see if that fixes it?
Or a log file or something in particular I should look at? I looked at var/log/messages and didn't see any failure when I searched for wlan0.
dancytron wrote: ↑Sat Sep 16, 2023 9:33 pmI haven't reported it before because I had a kind of weird Bullseye setup on my laptop and I can't really reproduce it, but I'm getting it now in Bookworm too, both conventional setup and experiments with systemd and pipewire. A search through var/logs/messages for wlan0 doesn't show any obvious failure.
About 20% of the time the wireless fails to connect on reboot. It doesn't see wlan0 and restarting Peasywifi doesn't help. I have to reboot to get it to load. Once it boots correctly, it works fine from then on.
It feels like a race condition where the wireless driver doesn't get loaded sometimes.
Is there someplace I can add some wait time to see if that fixes it?
Or a log file or something in particular I should look at? I looked at var/log/messages and didn't see any failure when I searched for wlan0.
With systemd boot I usually add net.ifnames=0 to the boot kernel line, but sometimes I forget and wlan0 doesn't exist, then have to look for what's the 'cryptic' name with ifconfig -a and change in /etc/pwf/pwf.conf to export INTERFACE=<crypric_name> .
Not sure though if that's the case for you too.
Thanks. I'll try that.
Discovery in my trying to make using the puppy user less of a pia. If you turn the password off for puppy user and use sudo with the xlunch scripts, it seems to cleanly launch applications as the sudo user. It's almost like root in a window.
Hi everybody,
I encounter difficulties after autologin I have a black screen I am on a 32bit build someone has the same problem
Thanks in advance
I've had similar problem, could be that the Bookworm kernel (6.xx) doesn't work ok on 32-bit.
Solution may be to swap the kernel with a 5.xx version, I can possibly share a "package" for that, tell me if you're interested.
Dear @fredx181
i forgot to mention "systemd mklive 32bit build"
thank's for reply
in rdp session : (error skl_dmc_ver1_27.bin fixed by "firmware-misc-nonfree")
'
'[ 20.949152] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 21.001119] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 21.012557] i915 0000:00:02.0: firmware: direct-loading firmware i915/skl_dmc_ver1_27.bin
[ 21.013228] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
[ 21.097812] i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
[ 21.097830] i915 0000:00:02.0: [drm] [ENCODER:110:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
[ 22.620314] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[ 22.697818] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 22.741670] fbcon: i915drmfb (fb0) is primary device
[ 22.807712] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
'
so now when i disable i915 (
i915.modeset=0
)
displayed desktop
I see that only one choice in displaying resolution select '1920*1080'
'Default Monitor' replace 'edp-1'
So now i know there is a mistake with i915
you think that i must to recompile intel driver ?
or there is an other source in conflict with i915 ?
In parallel i'll test games with this configuration but i think mesa vulkan driver will freeze and lags...
I'll find to force other resolution if no lags and freeze...
And to reply you yes i'm interested, i want just obtain the last version stable mes vulkan driver...
So i think the 5... kernel will be fine !
Thks in advance..
In evolution :
second mod [replace i915 find in k5.10.0.25 bulls + delete or activate i915.modeset=1] Not good similare at disable i915 because this driver not be compiled for this kernel ....
bobol wrote:so now when i disable i915 (
i915.modeset=0
Try: i915.enable_dc=0 and see if you got resolution choices.
looks very much like the problem I had, discussed earlier (solution given here: viewtopic.php?p=90186#p90186) with installed firmware-misc-nonfree combined with kernel 6.1.
hi @fredx181
no moore resolutions with
Code: Select all
i915.enable_dc=0in fact I would need several resolutions because certain games by wine are configured in VD (virtual desktop), and to properly do so the resolution of the OS at the same values resizes to the right size (almost fullscreen) and not in a mini window
I think you knew that... 
Thk you for your time...
Ok now i think i915 works
i just add (create) a /etc/X11/xorg.conf
(of course deleted i915.modeset=0)
[ I've not tested but i think it will fix too mklive-sid ]
Code: Select all
Section "Device"
Identifier "Device0"
Driver "intel"
EndSection
I think it will help some... 
Great solution @bobol !
Meanwhile I tested some more, turns out that on my newish Asus laptop I got the same problem (with 32-bit build) , blank screen after autologin, but on my very old HP laptop (from 2007) it's OK.
But the xorg.conf method is something to remember as a fix that often works.
have you try to reinstall
xserver-xorg-video-intel and vesa
...
I must have misunderstood, 
I understood that you had 2 PCs and that on one of the 2 you could not resolve the problem even with xorg.conf. 
Review after xorg.conf function i915
Very bad trip..
Very strange reacts with wine and vxdk..
Cannot activate dxvk, stays on opengl
Have you tried on your side ?
Sounds bad. Tried it on my side, yes, and works ok to choose resolution, but did not test with wine or dxvk.
Could be that 32-bit is not fully supported anymore, pity if so.
hi @fredx181 thank's for your reply
i'll try all posibility to resolve it... i come back after found or not..
i think it will be difficult. So i will post when the problem is resolved
First return :
i915.modeset=0 load fbdev driver Display with only 1 resolution
Code: Select all
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: fbdev
unloaded: vesa failed: modesetting dri: iris gpu: i915
resolution: 1364x768~50Hz
xorg.conf load intel driver Display multiple resolution with bugs/wine
Code: Select all
Graphics:
Device-1: Intel HD Graphics 515 vendor: Toshiba driver: i915 v: kernel
arch: Gen-9 bus-ID: 00:02.0
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: iris
gpu: i915 resolution: 1364x768~50Hz
API: EGL v: 1.5 drivers: iris,swrast platforms:
active: gbm,x11,surfaceless,device inactive: wayland
API: OpenGL v: 4.6 vendor: intel mesa v: 22.3.6 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics 515 (SKL GT2)other release (eg:bullseyedog), no problems startboot load modesetting driver No display
Code: Select all
Graphics:
Device-1: Intel HD Graphics 515 vendor: Toshiba driver: i915 v: kernel
arch: Gen-9 ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:191e
Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x576 s-dpi: 96
Monitor-1: eDP-1 model: Samsung 0x4350 res: 1024x576 dpi: 94
diag: 317mm (12.5")
API: OpenGL v: 4.6 vendor: intel mesa v: 20.3.5 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel HD Graphics 515 (SKL GT2)
device-ID: 8086:191eTested with release run no problems wine (d3d)
when i add xorg.conf (boot with intel), bugs with wine too
First impression : it's probably mean that modesetting_drv would be the cause or dependency around
Ok so now i can confirm that i915 driver run well with wine...
just added
Code: Select all
Option "DRI" "3"to xorg.conf
and my dxvk dll package caused problems
nothing too bad then
Changes in the custom repository:
-- removed 'gmplayer' from the custom repo (was custom build from years ago), alternative is "mplayer-gui" from Debian repo (apt install mplayer-gui mplayer-skin-blue)
-- peasymp3 depends now on mplayer (from Debian repo) instead of 'gmplayer'
-- gnome-mplayer ('gnome-mplayer-1.0.6' named on amd64) depends on mplayer now instead of the custom build mplayer binary (old version) that was included in the package
-- run-as-user package (similar to run-as-spot) updated, includes @jamesbond's newest improvements but modified for Debian dog.
Sounds good. 
I think I might have learned a few things with KLV. I'll try to make a shareable ISO this week.
Dan
Hi Fred,
Does this mean there's some update to the online .conf files?
I keep a set of local .conf files that I use when refreshing build.
If I want to check against latest conf files from online build, is the following place is best place to download them from?
https://github.com/DebianDog/MakeLive/t ... s-bookworm
https://github.com/DebianDog/MakeLive/t ... s-bullseye
Thank you.
dcung wrote:If I want to check against latest conf files from online build, is the following place is best place to download them from?
https://github.com/DebianDog/MakeLive/t ... s-bookworm
Yes, or here (web index page): https://debiandog.github.io/MakeLive/configs-bookworm/
Did NOT change these though, the changes as I mentioned are in the custom deb packages repo.
P.S. for mklive-sid I did change some configs, viewtopic.php?p=100404#p100404 (removed "initscripts" because was conflicting with systemd build).
Yes, I saw that last commit/update there was 2 months ago. But thought to double check.
fredx181 wrote: ↑Sun Oct 08, 2023 7:29 amP.S. for mklive-sid I did change some configs, viewtopic.php?p=100404#p100404 (removed "initscripts" because was conflicting with systemd build).
Ok, I'll update mine. Thanks for this info. 
@fredx181
FYI - Just reporting.
I refreshed my bookworm sets builds (NMU and non NMU) - all are okay, except...
for i386 with systemd, the following error.
Note - I used my local conf files, that were used last month, and were okay then.
Code: Select all
The following packages have unmet dependencies:
gnome-mplayer-1.0.7 : Depends: libldap-2.4-2 but it is not installable
E: Unable to correct problems, you have held broken packages.
[0;31mSorry, there are one or more errors, see above.[0m
[0;31mCould be a typo in a package name.[0m
[0;36mExiting . . .[0m
[0;36mUnmounting mount binds in chroot[0mdcung wrote: ↑Sun Oct 08, 2023 8:14 pm@fredx181
FYI - Just reporting.
I refreshed my bookworm sets builds (NMU and non NMU) - all are okay, except...
for i386 with systemd, the following error.
Note - I used my local conf files, that were used last month, and were okay then.Code: Select all
The following packages have unmet dependencies: gnome-mplayer-1.0.7 : Depends: libldap-2.4-2 but it is not installable ...
Yes, forgot earlier to add libldap-2.4-2 to the i386 repo for systemd, fixed now. Thanks!
i386 with systemd - build okay now.
Thanks Fred.
Hi @Fred ..
How to make the default user when we startx is puppy instead of root?
Thank you.
If you run without systemd change in /etc/inittab (probably line 53) :
1:2345:respawn:/bin/login -f root tty6 </dev/tty1 >/dev/tty1 2>&1
To:
1:2345:respawn:/bin/login -f puppy tty6 </dev/tty1 >/dev/tty1 2>&1
(when with running systemd it's different way)
Hi evereybody @recobayu
If you run systemd
edit /etc/systemd/system/getty@tty1.service
find line (probably 28)
ExecStart=-/sbin/agetty --noclear -a root %I 38400
change user choice (here root)...
non systemd follow @fredx181 instruction...