testing: a slacko without xorgwizard-automatic

Under development: PCMCIA, wireless, etc.
Message
Author
gcmartin

LAN routing is NOT occurring

#46 Post by gcmartin »

Scenario:
DVD boots an AMD X2 HP touch laptop to desktop. System has acquired an IP address by the time it reaches desktop from the DHCP server via the wired network. FirstRUN operations are same expected operations as have been seen over the years without issue.

Problem:
Routing over the LAN is NOT occurring. I have no obvious error indications except I can not get responses for simple pings, or any other LAN service from one PC to any other.

And, I cannot route thru to the internet. I had this problem before, on a DELL touch AIO. But, it is still with us and occurs on several networks I have tested over past 2 days.

Asking community
Requesting advice to assist discovery of the problem. This is unique to this PUP and was 1st discovered last year in FATDOG and NEVER resolved. Now it is here, in Slacko64-6xxx.

Most important to me is why in this PUP this has surfaced? None of the other distros; namely mainline distros, mainline OSes, every other PUP (excepting FATDOG) has never exhibited this problem. So, its either some major directional change in network behavior after it acquires its LAN personality from the DHCP host or something buried in WOOFCE.

This is NOT a static IP, and the DHCP hosts do NOT do static assignments of the IP to this laptop/DELL touch AIO.

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#47 Post by Marv »

@gcmartin,

What NIC is in this HP laptop? Driver used? And does it 'remap' eth0 to eth1? ie. when booting from a pup that works, what is the active interface and what does it show in this pup? Output of dmesg | grep eth? Just to help the thought processes.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#48 Post by 01micko »

Those with ipw problems.. I need you to try something.

The firmware for these devices is in /lib/modules/all-firmware/ipw* (there are 3 possible directories)

Can you try moving those 3 directories to /lib/firmware/ and reboot. See if connection can work then.

Thanks.

---------------

Thanks Marv - dmesg output may provide a key for many connectivity problems.
Puppy Linux Blog - contact me for access

unicorn316386

#49 Post by unicorn316386 »

^^ Just tried moving the 3 ipw* folders and rebooting, didn't seem to have any positive effect here it seems.

The "dmesg" output looks interesting though. Here's a section of diff between my 3.14.55 and 3.14.57 output:

Code: Select all

--- dmesg_31455.txt	2015-12-09 00:38:42.000000000 -0500
+++ dmesg_31457.txt	2015-12-09 00:30:17.000000000 -0500

@@ -774,7 +775,19 @@
 pps_core: LinuxPPS API ver. 1 registered
 pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
 PTP clock support registered
+tg3.c:v3.136 (Jan 03, 2014)
+tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM95751) rev 4001] (PCI Express) MAC address 00:12:3f:23:bb:55
+tg3 0000:01:00.0 eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
+tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
+tg3 0000:01:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
 cfg80211: Calling CRDA to update world regulatory domain
+lib80211: common routines for IEEE802.11 drivers
+lib80211_crypt: registered algorithm 'NULL'
+libipw: 802.11 data/management/control stack, git-1.1.13
+libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
+ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
+ipw2200: Copyright(c) 2003-2006 Intel Corporation
+[drm] initialized overlay support
 yenta_cardbus 0000:02:01.0: ISA IRQ mask 0x0cf8, PCI irq 19
 yenta_cardbus 0000:02:01.0: Socket status: 30000006
 pci_bus 0000:02: Raising subordinate bus# of parent bus (#02) from #03 to #06
@@ -784,19 +797,10 @@
 yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge window: [mem 0x40000000-0x43ffffff pref]
 pcmcia_socket pcmcia_socket0: cs: memory probe 0x40000000-0x43ffffff:
  excluding 0x40000000-0x43ffffff
-lib80211: common routines for IEEE802.11 drivers
-lib80211_crypt: registered algorithm 'NULL'
-libipw: 802.11 data/management/control stack, git-1.1.13
-libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
-tg3.c:v3.136 (Jan 03, 2014)
-tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM95751) rev 4001] (PCI Express) MAC address 00:12:3f:23:bb:55
-tg3 0000:01:00.0 eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
-tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
-tg3 0000:01:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
-input: PC Speaker as /devices/platform/pcspkr/input/input7
-ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmpr
-ipw2200: Copyright(c) 2003-2006 Intel Corporation
 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
+ipw2200 0000:02:03.0: Direct firmware load failed with error -2
+ipw2200 0000:02:03.0: Falling back to user helper
+input: PC Speaker as /devices/platform/pcspkr/input/input7
 Bluetooth: Core ver 2.18
 NET: Registered protocol family 31
 Bluetooth: HCI device and connection manager initialized
@@ -804,14 +808,12 @@
 Bluetooth: L2CAP socket layer initialized
 Bluetooth: SCO socket layer initialized
 usbcore: registered new interface driver btusb
-ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
 pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
  excluding 0xc0000-0xc7fff 0xcc000-0xcffff 0xf0000-0xfffff
 pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
  clean.
 pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
  clean.
-[drm] initialized overlay support
 fbcon: inteldrmfb (fb0) is primary device
 input: DualPoint Stick as /devices/platform/i8042/serio1/input/input8
 input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input6
@@ -819,8 +821,11 @@
 i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
 i915 0000:00:02.0: registered panic notifier
 [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
-intel8x0_measure_ac97_clock: measured 52571 usecs (2533 samples)
+intel8x0_measure_ac97_clock: measured 52521 usecs (2531 samples)
 intel8x0: clocking to 48000
+ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
+ipw2200: Unable to load firmware: -2
+ipw2200: probe of 0000:02:03.0 failed with error -5
 pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
  excluding 0xc0000-0xc7fff 0xcc000-0xcffff 0xf0000-0xfffff
 pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
Heading to bed but maybe I'll try playing around with this some more tomorrow. :lol: Thanks for this debugging tip.

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#50 Post by mavrothal »

unicorn316386 wrote:Here's a section of diff between my 3.14.55 and 3.14.57 output:
Is the kernel the only difference or dmesgs come different puppies?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

gcmartin

#51 Post by gcmartin »

Update to earlier post. The problem with laptop occurs with the 64bit, the 32bit, and with TahrPUP32-6041 on the touch laptop. I suspect it is due to its chipset. In each version, the distro discovers its lo & eth0 features, but NOT its wlan0 feature. This is apparent when the distro is booted to desktop, and allowed to settle for couple of minutes after the FirstRUN screen is shown. A terminal is opened to

Code: Select all

# ip address
I will have to post a inxi/hardinfo report a little later today for the laptop.

The other, the AIO PC, is currently, offline running a simulation. Will have to test it later to gather its report(s).

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#52 Post by Marv »

01micko wrote:Those with ipw problems.. I need you to try something.

The firmware for these devices is in /lib/modules/all-firmware/ipw* (there are 3 possible directories)

Can you try moving those 3 directories to /lib/firmware/ and reboot. See if connection can work then.
.
Try moving only the files in /lib/modules/all-firmware/ipw2200_firmware-3.0/lib/firmware directly into /lib/firmware. That has long been the workaround for ipw2200 problems. However, I think this time the problem is other than that as I had to drop back to the 3.14.55 kernel for quite a different NIC also. My guess is a depreciated 'user helper' component in the newer kernels. See the line with that entry in unicorn316386's posted dmesg above comparing the two kernels.

Update: Went and picked up an ipw2200 laptop that was due for software updates. Ran 32 bit 6.3.0.1 with the stock kernel, no connection. Reran with the 3.14.55 kernel, connection fine. Back to the 3.14.57 kernel, did the direct copy I outlined above and rebooted. Connection fine.
No 'user helper' error messages in dmesg. Posting from it now.

Edit: Kernel dropback mentioned in green above was due to slow booting only, not NIC related. Too many pups-in-the-pot.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

wireless

#53 Post by sheldonisaac »

Marv (in part) wrote: Try moving only the files in /lib/modules/all-firmware/ipw2200_firmware-3.0/lib/firmware directly into /lib/firmware
Marv, maybe you or someone else wants to help: I just put this new slacko from 01micko on my hand-me-down Dell Mini 9.

ifconfig -a can't see the Broadcom wireless card, BRCM4312, 14e4:4315
(SuperLupu 2 can see it, and connect)

So I opened the case and plugged in the Intel 6305 card; it can't see that either.

I'm an "old newbie", that is, a non-expert. Have not done compiling, kernel switching, etc

At your convenience, folks, could you suggest what to do?


Thanks,
Sheldon
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

Re: wireless

#54 Post by Marv »

sheldonisaac wrote: ifconfig -a can't see the Broadcom wireless card, BRCM4312, 14e4:4315
(SuperLupu 2 can see it, and connect)

So I opened the case and plugged in the Intel 6305 card; it can't see that either.

I'm an "old newbie", that is, a non-expert. Have not done compiling, kernel switching, etc

At your convenience, folks, could you suggest what to do?


Thanks,
Sheldon
NOT a broadcom guy... The most probable solution to that is to install the wl driver compiled for the kernel used and blacklist/skiplist b43 and ssb. There is a wl compiled for 3.14.55 available on the forum but not one for 3.14.57 so far as I know.

The intel firmware for the (6205 not 6305?) is not present but can be downloaded from the second link in this post http://www.murga-linux.com/puppy/viewtopic.php?t=97276 (just do all the iwlwifi-6000 ones) and placed in /lib/firmware. Reboot and retry.

More generally, This version of slacko is very much an experiment focussed on Xorg behavior and might not be the best to use for a first install. Several others have larger firmware package collections. Not trying to be a grinch :?
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

Re: wireless

#55 Post by sheldonisaac »

Marv (in part) wrote:The intel firmware for the (6205 not 6305?) is not present but can be downloaded from the second link in this post http://www.murga-linux.com/puppy/viewtopic.php?t=97276 (just do all the iwlwifi-6000 ones) and placed in /lib/firmware. Reboot and retry.
Yes, Marv, and thanks a lot for your reply! Magnifying glass confirms it is indeed a 6205.
More generally, This version of slacko is very much an experiment focussed on Xorg behavior and might not be the best to use for a first install. Several others have larger firmware package collections.
Understood, and thanks for pointing that out.
Last edited by sheldonisaac on Thu 10 Dec 2015, 12:43, edited 1 time in total.
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P

User avatar
Ghost Dog
Posts: 163
Joined: Fri 27 Jan 2012, 04:29

#56 Post by Ghost Dog »

Ghost Dog wrote:I'm trying to update xorg for Lucid, see here. Xorgwizard-automatic doesn't work anymore, though. How do I adapt this new method?
The Way of the Samurai

User avatar
Revolverve
Posts: 255
Joined: Sat 08 Nov 2008, 21:01
Location: 45°17'28.8"N 72°16'08.8"W_avatar/ mira.ca

#57 Post by Revolverve »

A plus,as in fatdog to have wacom+dual touch working OOTB.

User avatar
moeppyfan
Posts: 47
Joined: Thu 11 Feb 2016, 18:59

#58 Post by moeppyfan »

01micko wrote:Those with ipw problems.. I need you to try something.

The firmware for these devices is in /lib/modules/all-firmware/ipw* (there are 3 possible directories)

Can you try moving those 3 directories to /lib/firmware/ and reboot. See if connection can work then.

Thanks.
Hello 01micko,

Remastering the zdrv itself for 3.14.57 to include these 3 files in /lib/firmware fixes the detection and the delay. Example
Last edited by moeppyfan on Fri 26 Feb 2016, 04:38, edited 7 times in total.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#59 Post by s243a »

I'm a bit late to the discussion so sorry if I missed something. I have recently been trying to upgrade xorg for tahrpup which is a feet probably well beyond my skill level. Fatdog64 is my model because virtualbox mouse integration works on fatdog64 but not on tahrpup. I notice that fatdog64 has its own xorg wizard called fatdog-xorgwazard.sh that looks much simpler and cleaner than the one on tahrpup. Perhaps the fatdog xorgwizard can be used as a model for rewrites of the xorgwiard on other versions of puppylinux.

edit: Maybe I'm getting the xorgwizard script mixed up with the xwin script so I'm not doing an apples to apples comparison. I'll have to look at it closer when I get home.

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#60 Post by greengeek »

Very late to the party (didn't realise this topic existed!) - but just tried the 32bit version on an Acer Iconia Tab W501 and the touchscreen works beautifully!

Well done 01Micko this is a welcome advance.

I am so excited by this that I didn't try any other functions. I will have a further play when I get more time but one of the first things I want to try is to see if i can make a switcher script (maybe attached to a desktop or tray icon) to let me use the mouse pointer for either left click or right click functions as desired.

At the moment left click is perfect but no rightclick menu of course.

I recall reading something about Ubuntu (Maverick?I think?) recently which showed something similar so i will see what I can find. Now that I think about it that was a youtube vid showing Ubuntu on a Dell Inspiron Duo tablet. I will try this Slacko on one of those Dell Duo's as soon as I can (cuppla days...) and report back.

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#61 Post by greengeek »

Posting this using the 32 bit Slacko from a Dell Inspiron Duo which has the unusual feature of allowing the screen to rotate 180 degrees so that it can be used as a netbook (mini laptop) or as a touch enabled tablet. Very excited by this as the touchscreen works great and seems accurate.

Screen res is high so everything seems a little small for my fat fingers but working pretty well nonetheless.

I will find a suitable version of xvkbd and do some more in depth testing.
Couple of oddities so far - the leftclick mouse button doesn't seem to work (EDIT: "sometimes"). Not sure if thats hardware or software related yet. Also I seem to get variable response when I tap the main menu button - seems like the software has the ability to differentiate between a quick tap and a long one. Dunno. more testing to follow.

Here's my report-video:

Code: Select all

VIDEO REPORT: Slacko Puppy, version 6.3.0.1

Chip description:
VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02)
Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02)
Multimedia controller: Broadcom Corporation BCM70015 Video Decoder [Crystal HD]

NOTE: there is no /etc/X11/xorg.conf configuration file.

Probing Xorg startup log file (/var/log/Xorg.0.log):
  Driver loaded (and currently in use): intel
  Loaded modules: dri2 evdev fb glx synaptics

Actual rendering on monitor:
  Resolution:  1366x768 pixels (361x203 millimeters)
  Depth:       24 planes

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#62 Post by 01micko »

There *should* be a version of xvkbd in the repo (you may need to update it). look for 'x-keyboard' too. It should install a status icon that controls xvkbd just by tapping on it.

Also, for the iconia I have rotation working :) .. but I haven't looked at it for a while and I can't recall if I uploaded packages. I do have an 'adrv' though that will load automagically. I'll post that somewhere soon.
Puppy Linux Blog - contact me for access

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#63 Post by greengeek »

I recall on some puppies having been shown how to increase the dpi setting of the display in order to change the size of icons etc - but I can't remember how this is done.

I can't seem to get into xorgwizard to make any changes (obviously) so I am wondering if there is some method to change dpi? I want to do this to try and improve sizing of icons and tabs for touch use.

I am experimenting with a variety of methods to improve usability on a Dell Duo tablet.

Thread here

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#64 Post by greengeek »

I know bug reports are not being sought but I would like to request any pointers that people could give me to try and improve the desktop icon placement please as it is affecting useability on a touchscreen (and this is the first puppy that I have got anywhere near functional for real productive touchscreen use...)

I would like to alter the position of the desktop drive icons so that they are higher. Currently they "underlap" the bottom jwm tray and the drive labels are not fully visible.

I have looked at several files and think theses are the two most relevant:

/etc/eventmanager
/usr/local/pup_event/frontend_funcs

I also looked at /sbin/pup_event_frontend_d - which carries the note:"#have replaced pup_event_frontend_d script with compiled daemon." - but I don't know what that daemon is or who wrote it - so I don't know if it is involved or not.

I suspect the file that is most involved is /usr/local/pup_event/frontend_funcs but it references some definitions for geometry of drive icon placement within /etc/eventmanager - for example the following definition seems to be relevant to drive placement:

Code: Select all

#091208 adjust drive icons placement, read by /sbin/pup_event_frontend_d
#gap between icons and edge of screen (>0 if need to leave space for a tray)...
ICON_PLACE_EDGE_GAP=64
#indent from edge before icons start...
ICON_PLACE_START_GAP=32
#spacing between successive icons (64 matches other icons on desktop)...
ICON_PLACE_SPACING=64 #56
#left, right, bottom, or top of screen...
ICON_PLACE_ORIENTATION='bottom'
The file /tmp/pup_event_frontend/scrn_x says 1280 and scrn_y says 800 (ie res = 1280x800)

I have tried changing the "ICON_PLACE_EDGE_GAP to 128 and sure enough it does lift the usb drive and optical drive icons well above the bottom tray - but it leaves the icons for the inbuilt drives exactly where they were as seen in the pic below.

Does anyone have any suggestions how i can correct the low placement of the icons?

cheers!
Attachments
drive_placement.jpg
(8 KiB) Downloaded 930 times

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#65 Post by Sailor Enceladus »

@greengeek: In Menu -> Desktop -> Desktop drive icons manager I found a checkmark called "Refresh / Realign existing icons". Changing Edge Gap to 128 there then clicking that checkmark and pressing Ok made my sda icons disappear, then they reappeared 20 seconds later at a higher position (128 pixels from the bottom I guess). This is in Slacko 6.9.6.1 though.

Post Reply