Boot off LIve CD
Select Xorg video
Wait 10 seconds
Get the "Your mouse has not moved" message
Select usb/ps2 and click OK (the mouse is USB)
Screen refreshes
Mouse pointer disappears!
A full reboot is required.

Boot off Live CD
Select Xvesa
Don't get the Welcome popup message
Mouse works correctly

Thank you, rcrsn51. My reports here aren't always heeded nor believed because I am not one of the inner circle of coders. However, as a dispassionate scientific observer and reporter, I suspect I have as much experience and credibility as any, not least because experience accrues with age! So thanks my friend for confirming my earlier report on this occasion.

OK, just managed to confirm reported effects on a couple other spare machines running single core AMD, 1/2 - 1Mb mem. and ATI cards. The strange mouse and screen behaviours are always replicated from a live pfix=ram boot but the blank screen detente seems to vary from 10 - 30s between boxes. In this respect, these are entirely new features.

I suspect that Barry's sound card issue (reported in his blog) is only a symptom of a larger problem. The default sound card is expected to be number 0, but the number is assigned by backend_modprobe (or ALSA's autoloader, if used) first-come-first-served. So the choice is affected by the timing of hardware initialization and related event generation. (Without its 2-second delay, the agrsm firmware blacklists 3 built-in modems that could otherwise grab number 0 before the actual sound card gets it.) In wary and woof, it appears also that until the alsa wizard is run, the number gets re-chosen on each bootup, which would account for inconsistent sound behaviour.

Although I have addressed all of this in my "modprobe protect" function, the wary/woof replacement for it does not. I found good information in the alsa-base.conf file in Lucid Puppy, originally from ubuntu and debian. Besides some install statements for built-in modems, it contains a section that prevents non-sound-card drivers from using card number 0 -- ALSA modems , video-capture cards and some USB sound devices.

My guess is that with the ALSA autoloader the ALSA drivers interpret an index value of "-2" to mean to skip number zero during assignment. Although I cannot find a straightforward declaration about that value, all indications from googling are that it means this. Apparently, the drivers obtain their numbers somehow, although Puppy takes over that function, pre-empting the drivers' need to be further assigned. Anyway, I believe that Puppy needs to implement the avoidance of non-sound-card devices from getting number zero when it assigns the numbers. In addition, it should retain the setting for card zero across reboots -- commonly reported as a problem.

Because of the complexity of wary/woof's number assignment technique, I must leave it to Barry to implement these improvements in woof. A start would be to either adopt the debian/ubuntu alsa-base.conf configuration file or include most of its content in alsa.conf, and add backend_modprobe logic to use that information to determine the devices that must not use "0" unless overridden by the alsawizard (to use the USB sound devices).

OK, just managed to confirm reported effects on a couple other spare machines running single core AMD, 1/2 - 1Mb mem. and ATI cards. The strange mouse and screen behaviours are always replicated from a live pfix=ram boot but the blank screen detente seems to vary from 10 - 30s between boxes. In this respect, these are entirely new features.

He reported part of what I saw. The mouse prompting only occurs if one is not sitting in anticipation - appears after some several seconds; I am usually doing more than one thing at a time. Cannot see any valid reason for its appearance.
Answer: I was able to release an nV card last night and confirm the screen blanking is not ATI-specific. With the nV card, the prompt screen is briefly flashed during blanking. Effect is present with both Dell (always a weird one) and bog std. AOC monitors. Not able to test with crt at this time. Swap space always available; can't think of any other non-std. HW aspects.

I was discussing a problem with sound with rerwin just prior to releasing Wary 5.1.1.56, but deferred it until now. Rerwin has outlined the issue in his above post.

It may be that the solution is extremely simple. Originally, I had code in /sbin/pup_event_backend_modprobe to assign card slot numbers.
However, the existence of /etc/modprobe.d/alsa-base.conf changes the ball game entirely.

I have simply removed my slot assignment code in pup_event_backend_modprobe. It works fine on my laptop.

I would welcome testers.

Step 1
Could you please download 'alsa-base.conf.gz', ungzip it and place at /etc/modprobe.d.

Step 2
In /etc/modprobe.d you will see one or more files named like this:

alsa_card3049.conf

where you will have some number different from '3049'. Delete those files.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum