Woof-CE System changes that need testing.......

Under development: PCMCIA, wireless, etc.
Post Reply
Message
Author
User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Woof-CE System changes that need testing.......

#1 Post by peebee »

https://github.com/puppylinux-woof-CE/w ... ssues/1524

https://github.com/puppylinux-woof-CE/w ... e3564e1a4a

affects /usr/bin/xwin
and
/etc/rc.d/rc.sysinit

Need testing...........

Rename the attached ydrv to suit your install and reboot - suggest only test on a pristine frugal install with no personal save
Attachments
ydrv_19.06.sfs-false.gz
remove -false.gz
(16 KiB) Downloaded 140 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

foxpup
Posts: 1132
Joined: Fri 29 Jul 2016, 21:08

#2 Post by foxpup »

There is almost never a ydrv. So this is additional to the regular pristine frugal.

What should the test be?
Just boot?
On older/newer machines?
Older/newer Puppys?

btw, this is dpupStretch RC4 with the ydrv.
Boots just normally. Keyboard, mouse, wifi good.

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#3 Post by perdido »

Hi peebee,

Test conducted on a Dell e6400 based laptop

Downloaded and renamed ydrv to ydrv_upupbb_19.03.sfs and copied into directory with the upupbb_19.03 files

Booted upupbb_19.03 as frugal install with no save file or save directory.
ydrv loaded during boot. No hangs.

It produced the /dev/disk/ directory with 5 subdirectories, attached a screeny of /dev/disk/
I can do a tree of the whole directory structure if you need to see that.

.
Attachments
Screenshot.png
(41.39 KiB) Downloaded 563 times

ozsouth
Posts: 858
Joined: Fri 01 Jan 2010, 22:08
Location: S.E Australia

#4 Post by ozsouth »

LxPupSc_19.06 & ScPup64_19.01 using my 4.14 kernels (.134-32 & .131-64).
Both booted & mounted other drives ok. Both had 3 folders under /dev/disk - by-id; by-uuid & by-partuuid.
When usb stick inserted, by-path appeared - disappeared when usb stick withdrawn.

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#5 Post by mistfire »

Even in older rc.sysinit. The proposed lines of code works fine for me.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#6 Post by BarryK »

The attached files might be useful for wdlkmpx and other woof-CE developers.

In EasyOS, I simplified udev in rc.sysinit years ago, also took out 'udevadm settle'.

Instead of waiting for that "settle", just charge ahead, and have put some waits in elsewhere. For example, wait for the kernel video drivers to load in /usr/bin/xwin.

It seems to work OK.

Note that there is a lot of code in rc.sysinit that is different from the woof-CE version, as I forked my woofQ from woof2 ...I think about 6 years ago... for Quirky and then EasyOS, and there has been gradual divergence.

Anyway, the udev part might give some ideas to the woof-CE developers.
Attachments
xwin.gz
Remove the false .gz
(12.92 KiB) Downloaded 170 times
rc.sysinit.gz
Remove the false .gz
(27.58 KiB) Downloaded 162 times
[url]https://bkhome.org/news/[/url]

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#7 Post by mistfire »

I noticed that using the revised rc.sysinit. The boot time was longer by 20 seconds. Setting the udevadm settle timeout to 1-3 second is enough to kick start the udev properly

Post Reply