testing: a slacko without xorgwizard-automatic

[James C]

Just experimenting.....booted Alienbob's new Slackware Live iso
http://alien.slackbook.org/blog/slackware-live-edition/ ........ it first booted to the distorted display with nouveau then automagically reverted to modesetting. It took a couple of minutes but booted to a desktop.

Code: Select all

bash-4.3$ uname -a
Linux darkstar 4.1.13 #1 SMP Fri Nov 13 18:16:47 CST 2015 x86_64 AMD FX(tm)-8320 Eight-Core Processor AuthenticAMD GNU/Linux

[Marv]

32 bit 6.3.0.1 Frugal Grub4Dos install to 80Gb SATA HD on Bay-Trail desktop (Celeron J1900 CPU, RTL8168g NIC, intel i915 dvr graphics, PS2 mouse, US keyboard). 64 bit done previously on this desktop.

boots to desktop ok
keyboard works (US only to test)
PS2 connected generic scrollwheel mouse works
USB detection and hotplugging fine

wired network connection automatic at boot using RTL8168g NIC
sound ok

glxgears working, FPS as expected for this desktop.
kernel changed to 3.14.55, no discernable differences.

[Ghost Dog]

I'm trying to update xorg for Lucid, see here. Xorgwizard-automatic doesn't work anymore, though. How do I adapt this new method?

[gcmartin]

A very interesting occurrence in testing this "Proof of Concept".

Firstly, thanks @01Micko, I can see where you are guiding us in the community. Excellent.

On this Slacko version, I downloaded, created a DVD, and booted this on a 6-7 yr/old HP Touch laptop used for seminars.

On initial use, before FirstRUN completion, I tried screen touches: "touching" was not there. So I walked away on Saturday not doing much more, except to leave it running on a table in the house. This morning, I find that on-screen finger-tracking is WORKING!

Nothing has been done on my part. Thanks for where this is heading.

[Dry Falls]

2014 acer-aspire all intell box here which is notoreious for not booting newish pups to desktop had no problem with 6.3.0. 6.3.0.1 or 6.3.0.2. Very nice. Also compliments on the pupsave upgrade script. oh by the way, it's slacko64.

df

[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.

[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.

[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.

[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. Thanks for this debugging tip.

[mavrothal]

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?

[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).

[Marv]

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.

[sheldonisaac]

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

[Marv]

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

[sheldonisaac]

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.

[Ghost Dog]

I'm trying to update xorg for Lucid, see here. Xorgwizard-automatic doesn't work anymore, though. How do I adapt this new method?

[Revolverve]

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

[moeppyfan]

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

[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.

[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.