Puppy 4.1.1 (2.6.25.16 kernel) final - bug reports

Please post any bugs you have found
Message
Author
User avatar
Botanic
Posts: 240
Joined: Wed 05 Sep 2007, 10:54
Location: Toulouse, France

#61 Post by Botanic »

now that's funny because Puppy auto-repaired the keyboard mapping, i don't know how...

I should first find out the difference between a gtk theme and a gtk engine, then try to figure out how drivers work in Linux - my xorg problem is maybe monitor-related (i use a CRT 21' monitor, not very commonplace)
Puppy 2.16 on HP Vectra VL400 - PIII 800 MHz - 320M RAM
Wary on Acer Aspire X3200 - Phenom X4 - 2.2GHz - 4G RAM

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

#62 Post by Dougal »

Botanic wrote:I should first find out the difference between a gtk theme and a gtk engine
An engine is a binary located in /usr/lib/gtk-2.0/*/engines and is responsible for enabling you to draw fancy looking widgets.
A theme is just a text file (gtkrc) located in /usr/share/themes, possibly accompanied by some icons and which just tells gtk what to draw each type of widget like and which engine to use.
You were using a Ubuntu theme that requires the ubuntulooks engine (most likely a Ubuntu version of the clearlooks engine) and the crux engine.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

User avatar
Botanic
Posts: 240
Joined: Wed 05 Sep 2007, 10:54
Location: Toulouse, France

#63 Post by Botanic »

Thanks Dougal;
i can see ubuntulooks and crux-engine in my gtkrc file
Puppy 2.16 on HP Vectra VL400 - PIII 800 MHz - 320M RAM
Wary on Acer Aspire X3200 - Phenom X4 - 2.2GHz - 4G RAM

User avatar
Lobster
Official Crustacean
Posts: 15522
Joined: Wed 04 May 2005, 06:06
Location: Paradox Realm
Contact:

#64 Post by Lobster »

8) Hi guys,

Pretty sure this is a known bug but not sure where it has been reported.
Basically rox is reporting the file sizes as wrong (on a detailed listing) However if you right click on the file and click on properties, the correct size is available.

If anyone would like to report it to the rox team here is where . . .
http://roscidus.com/desktop/node/139
Puppy Raspup 8.2Final 8)
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html :D

pupshock
Posts: 140
Joined: Fri 23 Mar 2007, 05:30

Re: Wireless wont turn on in 4.1.1?

#65 Post by pupshock »

kattami wrote:Hi.
I have an FS Amilo Si 1520 and the wireless card is Intel PRO/Wireless 3945ABG.
In Puppylinux 3.01 the wireless worked. ......
But in Puppylinux 4.1.1 nothing happens when I push the button to turn on the wireless. While it is working in winxp and Debian distro when I tried that.
Only thing I can see from the network module list is that the driver thats used in 4.1.1 must be iwl3945.
I have the same problem:
wifi of my Thinkpad R60e is unable to connect, and the wifi light is off.
The iwl3945 module loads, and the network wizard 'SCAN' button reveals networks.

This Thinkpad R60e had no wifi problem with puppy 3.01:
Wifi light switches on at boot, ipw3945 loads (not iwl3945), and connection is a breeze.

--------------------------------------------------------------------------
Here are relevant statements from puppy 4.12's bootkernel.log:
--------------------------------------------------------------
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
.....
Marking TSC unstable due to: TSC halts in idle.
.....
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23ks
iwl3945: Copyright(c) 2003-2007 Intel Corporation
.....
ACPI: PCI Interrupt 0000:00:1f.3[A] -> GSI 23 (level, low) -> IRQ 23
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Adding 1052248k swap on /dev/sda3. Priority:-1 extents:1 across:1052248k
iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-3945-rs'
ACPI: PCI interrupt for device 0000:03:00.0 disabled
Clocksource tsc unstable (delta = -287901086 ns)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 100102, writing 100106)
.....
ACPI: PCI interrupt for device 0000:03:00.0 disabled
---------------------------------------------------------------------------

In comparison, puppy 3.01's bootkernel.log has:
-----------------------------------------------
ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.2d
ipw3945: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:03:00.0 to 64
ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
.....
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
----------------------------------------------------------------------------

As the problem is possibly related to a kernel issue, i tried various kernel boot parameters.
After much rebooting, these do not work:
pci=routeirq, acpi=force, irqpoll, nopcmcia, and their combinations.

Apart from
1. trying puppy 4.12 retro kernel 2.6.21.7
2. remaining with puppy 3.01,

does anyone have any ideas how to solve this wifi issue?

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#66 Post by rjbrewer »

The ipw3945 module is not in 4.1.1 new kernel or 4.1.2 new kernel;

but it is in 4.1.2 retro.

hope it helps.

rjb

Post Reply