On the 945gm Latitude the fps jumped from 20fps to 300
fps.
Unfortunately, when I rebooted it wasn't possible to restart
x. May be related to running frugal as I don't have a hard drive
for that machine yet and I always use full installs if possible

Same here, and I use frugal installs.

Were you able to recover from the X problem?

I'd really like to know how such a system (say from a blacklisted i915) could be repaired without trashing the personal savefile and starting over.

Is it possible to un-blacklist a video module if you can't start X and you get a black screen with blinking cursor, and no key response.

I did try pfix=clean in the grub menu.lst stanza but that made no difference to the start up problem. Didn't try pfix=purge.

Seems like there might be a less extreme alternative means if you could boot to terminal and then load the blacklisted module, and then do an xwin to boot to X with module in place. Then use Bootmanager to un-blacklist the module. Then re-start.

But what pfix line boots to cursor, and what are the commands to load a module from console, say i915?

I'd like to just know this stuff in case of any similar future X problems.

Newer Intel graphic chips (900+) and goo' old Xorg-1.3.0 intel_drv.so from Puppy-4.3 don't play very well together .

Newer Xorg-1.7+ since Lupu should be fine with i915.ko and Xorg's driver intel(_drv.so) .

Blacklisting using the bootmanager adds to the modprobe configuration file used to autoload kernel drivers at boot time (/tmp/modprobe.conf) . Xorg itself seems to be capable to load drivers itself and won't care about /tmp/modprobe.conf . Former puppy modprobe-v3.6 seems to be patched to automatically obey /etc/i[modprobe.d]/[modprobe.conf]* blacklist DRIVERNAME entries , while it is not the default . To make modprobe command obey blacklist entries , modprobe has to be aliased in configuration files like "alias modprobe='modprobe -b'" in /etc/profile , same as already "ls" is aliased there .

To load i915 for example :

Code:

modprobe -v i915 modeset=0

or

Code:

modprobe -v i915 modeset=1

What modeset actually does is still not clear to me ...

There is also the insmod command, but it requires the full path/driver-file-name.extension :

Thanks very much Karl Godt and npierce, that information is very very valuable to understand, and to have. I'm writing it in a little notebook I keep by the computer. I guess it would be a good idea to add all of the pfix commands there, too.

Possible bug -- just mentioning it here as a bug report -- I've raised a separate request for personal help on this in the regular User's forum.

Symptoms:

After a couple weeks of using Racy53, I'm suddenly getting many instances of a process called kworker. These use up processor resources to the point that the OS is inoperable a few seconds after X starts. I have to hard reset with the on-off button. Menu shutdown, Alt-Ctl-Del doesn't work. Can't open a terminal for poweroff, either. Well maybe if I could do it quick enough.....

The computer is listed in the sig below. This computer and Racy53 were working fine yesterday evening. I haven't installed any hardware or software since then, or made any changes at all. I did not have any hard shutdowns, or suspends before this occurrence. Now I have, of course.

Thank you Karl. The problem is suddenly gone, but I would still like to try to pin it down if we can, anyway.

The only difference I can see between multiple attempts to start up this morning, and starting up now, is that I moved my physical location. I was at a coffeeshop this morning, and am home now, so I'm wondering if it is related to wireless connection processes.

My understanding now is that kworker processes are actually place holder processes for other processes. Possibly wireless was one of those.

In older kernels pprocess or top would list actual processes running, but now these are seen as kworker processes -- so it is a lot harder to tell what is actually causing the hang up.

I like the older system better where you could actually see what was going on and what the cause was.

Anyway, to answer your questions, Karl, I don't have Radeon graphics. It is a laptop with integrated graphics using Intel Second Generation Core Processor graphics.

And a newly found one is that the default /root/.packages/woof-installed-packages has the DEV packages listed. Means they don't appear in PPM with the extra boxes ticked, even though not installed, so you can't install them from it._________________Puppy T290 - BarryK's Racy but with T2 Version 9.0. Beta's out soon!

Okay I can confirm that the overloading of the processor I brought up earlier here occurs as a result of moving to a wireless location (local cafe) with a large number of wireless networks in the vicinity. It completely blocks the mouse button effectiveness, programs, including terminal can't be opened, and CTRL-ALT-DEL (or backspace) have no effect, and I have to hard shutdown with the reset button. I can open another version of Puppy frugal, and connect fine with the same computer, in the same location. For instance, I am writing this on Upup Precise in the same location right now. This issue is only happening in Racy 53. It absolutely cripples the computer within seconds of X starting.

Refining the problem even further, I deleted the wireless profile for the cafe where the X start lock-up was occurring. That solved the problem when tested at that location. So something about that profile was causing the Puppy Network Wizard wireless manager to suddenly use all of the processor's capacity.

While this has solved my immediate problem, it's still a bug without a clear cause, and could happen again.

The kworker instances are probably just a symptom of what is going on with the wireless connection manager with a certain profile. Wish I knew what that is, but the profile was deleted.

If it happens again, I'd like to remove the profile but save it somewhere -- can someone tell me where the Puppy Network Wizard profiles are kept?

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