(old)Puppy Linux Discussion Forum

Had another old box running so 5.X.3.2.9 live pfix=ram. Since I was spared the usb mouse problems still running 5.X.3.2.9.
Everything working and correct on initial boot .... including a dreaded Logitech usb mouse.

# report-video
Dpup Exprimo, version 5.X.3.2.9 on Mon 5 Mar 2012

Chip description:
2.0 VGA compatible controller
Intel Corporation 82865G Integrated Graphics Controller (rev 02)
oem: Intel(r)865G Graphics Chip Accelerated VGA BIOS
product: Intel(r)865G Graphics Controller Hardware Version 0.0

X Server: Xorg
Driver used: is

X.Org version: 1.7.7
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz

Naturally really using the "Intel" driver.

-Computer-
Processor : 2x Intel(R) Pentium(R) 4 CPU 3.00GHz
Memory : 1025MB (179MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Mon 05 Mar 2012 07:35:44 PM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH4 - Intel ICH5

-USB Devices-
-UHCI Host Controller-
-UHCI Host Controller-
USB-PS/2 Optical Mouse
-UHCI Host Controller-
-EHCI Host Controller-

# free
total used free shared buffers
Mem: 1025296 535148 490148 0 64596
-/+ buffers: 470552 554744
Swap: 2150396 0 2150396

I had never any problem with my tree year old Logitech USB laser mouse.

For turther information pls look at the enclosed picture.

Cheers, Feodor

very nice, pemasu.
however, a problem is when i press ` or i use right click on rox, then terminal here, the urxvt don't appear.
how to fix that?
thanks.

I had the same problem that was reported for the 3.2.9 kernel with Logitech mouse not being detected until the usb receiver was removed and reinstalled. That problem has been corrected with this recompiled kernel.

Great to hear, I had this problem, so I am downloading 5.X.3.2.9.2 now.

I had never any problem with my tree year old Logitech USB laser mouse.

The problem does not affect all Logitech USB mice.
When I used my old Logitech USB mouse with 5.X.3.2.9, there was no problem.
When I used my new "Unifying" mouse and keyboard with 5.X.3.2.9, the problem occurred.
This is consistent with the description of the module as posted by "pemasu" a little while back.

gyro

Just to confirm that 5.X.3.2.9.2 fixes the problem I was having with my Logitech "Unifying" USB wireless mouse and keyboard.

gyro

Thank you all...of the reports of Logitech devices. It looks that gyro`s finding about Logitech new module is correct. New unifying feature needs to be compiled in.
One device-kernel bug fixed.
Thank you gyro and all testers....I am pleased

Everything looking very good so far... All areas tested so far, 'no problems.' Looks like this might be a good kernel to stay with for awhile!

One minor thing... this keeps popping up when program loads. We had the same issue back with earlier testing in Slacko and 01micko just said to # before a certain code line, I forget where that was but anyway, was wondering 'WHY' this appears anyway? And, are others getting this notice on startup?

>>>---Indian------>

Hi Pemasu !
Installed dpup exprimo 3.2.9 (not 3.2.9.2 ) to harddisk .
Could not find my networks (but my wlan interfaces are found )
From live cd and from USB stick install this networks are found internet is working , but not from a harddisk install .
The same with 5X13.6 SMP .
(have a single-core processor ).
Dpup EXPRIMO 5X13 single-core works well with wireless on harddisk install .

sszindian. No I dont get it. I get cpu temp info through sensors input ok.
I suppose we need to ask 01micko about the solution. It sounds like quite simple editing is needed.
Have you run in console: # sensors-detect ...and does it fix the popping up ?

backi. Inside Frisbee > wireless diagnostics > generate diagnostic data and post the generated package here.

Here are the generated diagnostic files .
I am not able to interprete that

RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b1a len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Cached scan results are empty - not posting
No suitable AP found.

It does not find any wireless networks.
And a lot apps segfaults: freemem_applet, vattery-acpitool, delayedrun etc....
I think this core 2 and up is not suitable wholly to your uniprocessor comp.

pemasu wrote:sszindian. No I dont get it. I get cpu temp info through sensors input ok.
I suppose we need to ask 01micko about the solution. It sounds like quite simple editing is needed.
Have you run in console: # sensors-detect ...and does it fix the popping up ?

backi. Inside Frisbee > wireless diagnostics > generate diagnostic data and post the generated package here.

Didn't report it but I was getting the same error message on Intel P4 boxes.... never appeared on my AMD boxes. Since I was just running live I never bothered with "sensor-detect" here.

What comes to my mind...you could test if manual coretemp module loading helps.
In console: # modprobe coretemp

If I'm remembering correctly, the message only appeared on single threading P4's ....... don't believe it appeared with the hyperthreaded P4 at the top of this page.

James C wrote:If I'm remembering correctly, the message only appeared on single threading P4's ....... don't believe it appeared with the hyperthreaded P4 at the top of this page.

Yeah...I enabled hyperthreading...so your hyperthreaded P4 should feel home with this kernel.

pemasu wrote:What comes to my mind...you could test if manual coretemp module loading helps.
In console: # modprobe coretemp

Booted 5.X.3.2.9 live in the regular P4. Error message appeared.Checked "sensors" under Hardinfo .....blank. Ran "modprobe coretemp" in terminal and rechecked "sensors" ....still blank.Restarted X and error message reappeared.

EDIT: Running "sensor-detect". Found a SMSC LPC47M172 Super IO Fan Sensor and reports success.However,at the end of the process the terminal reports that there is no driver for that sensor available.
EDIT 2:
Went ahead and upgraded the frugal install to 5.X.3.2.9 while I'm already there. See what it does from an install.

Error message continued to appear in a fresh frugal install. My quick and dirty workaround ....... I deleted "temp2tray" from /root/startup/ ....... no more error message.

MT-Paint-40

When an area is selected for 'Copy'... then a new graphic is loaded to paste it into... The 'paste' item hides itself at the r/h bottom of the screen, all that is noticeable is broken-line of the top of the paste item. You can (very carefully) click on that broken-line and drag the paste-item up but, it's a real pain and most not familiar with the graphic program will never find it!

>>>---Indian------>

pemasu wrote:
-----------------------------------------------------
sszindian. No I dont get it. I get cpu temp info through sensors input ok.
I suppose we need to ask 01micko about the solution. It sounds like quite simple editing is needed.
Have you run in console: # sensors-detect ...and does it fix the popping up ?
------------------------------------------------------

Yes I tried that and it doesn't fix it! The '# line' fix is posted in Slacko development somewhere where I was kidding 01micko about throwing 'pretty pink' notices at us and James C said... 'I thought it would just go away!!! 'Thanks for remembering James C!'

>>>---Indian------>

An Exprimo will boot straight to desktop without stopping on its initial boot should this be added or appended to kernel-append line This is the default. This means that Exprimo will get all of its localization settings at desktop, FirstRUN, rather than stopping along the way.

Just a note for the next Exprimo build.

Hope this helps