Puppy 2.17beta available

Under development: PCMCIA, wireless, etc.
Message
Author
zygo
Posts: 243
Joined: Sat 08 Apr 2006, 20:15
Location: UK

#41 Post by zygo »

I booted the live cd in ram without access to a pup_save. Cups worked with a plain text doc from abiword on my parallel hp deskjet plus. Nice and quick. It didn't work from leafpad (as it did in 2.16) nor geany though. To add the printer in cups I selected dj 500 because my printer was not listed. Where is the hpij pet that the instructions mention?

The time is now correct.

Thanks

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#42 Post by BarryK »

zygo wrote: Where is the hpij pet that the instructions mention?
Click 'install' button on desktop, and it should be listed in PETget. I haven't uploaded all the new PET packages yet, but that one is.

cthisbear
Posts: 4422
Joined: Sun 29 Jan 2006, 22:07
Location: Sydney Australia

#43 Post by cthisbear »

As previously reported on your news blog:

Asus P5GC-MX board.
The network card won't run...Attansic L2.
Spent an hour on this including using your Windows driver wizard.
This included the setup files, program files, Windows installed files.
I can generally cheat Windows into getting drivers to work from
previous installations...where many others may fail.
So I know where to look for - inf - files.
This will be a future issue as people upgrade to this board as a new box is
so cheap...my customers machine cost $280 to upgrade...
DVD extra $50

............................................................
Pentium Dual Core Upgrade Kit

Intel Pentium D 3.0 GHz CPU w/ 4MB cache
Asus Motherboard P5GC-MX
512 MB DDR 2 RAM
integrated Intel Graphics media Accelerator 950, w/ DX 9 support, 2048x1536@75Hz
ATX Case with front access USB ports
Onboard Lan, Sound, PCI express slot
.........................................................
Pity everythng worked but the Lan.
And the Asus site is a joke.
.........................................................
"
Attb2 said on 2007-04-21: (permalink)

* Attansic L2 fast ethernet dirver for Linux (ATL2) (77.4 KiB, application/rar)

Huang Xiong (from Attansic) emailed me the attached driver.

This works with feisty 2.6.20-15 kernel. Please integrate it to the next release!
I've tested it on Asus F5R notebook."

https://bugs.launchpad.net/ubuntu/+sour ... +bug/77725

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This might be a handy site for tested Linux computers:

http://www.linux-tested.com/results/

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
What about this? From Ubuntu forums;

http://ubuntuforums.org/showthread.php?p=2696399

" Re: Attansic L2 Fast Ethernet not detected
Quote:
Originally Posted by rabossa View Post
Em sembla a mi que en ixe nick vas a ser català, xD.

I recently bought a ASUS P5GC-MX MainBoard, and it has an Attansic L2 Fast Ethernet on it.
I compiled the module for make net working, and it just worked.

I attach the compiled module:
Attachment 33221

You had to move it to /lib/modules/<KERNEL VERSION>/kernel/drivers/net/atl.ko (I suppose that this is for convention), and then
Code:

insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/atl.ko

Then, your interface ethX, will appear on the NetworkManager.

Salutacions. "
//////////////////////////////////////////
and then further:
" harvey28 harvey28 is offline
First Cup of Ubuntu

Join Date: May 2007
Beans: 2
Re: Attansic L2 Fast Ethernet not detected
Hi everybodey, I found some drivers and it works! http://launchpadlibrarian.net/738241...driver_new.rar "

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
If you fix this Asus thing I'll have to call you Bazza Kacadbra .

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Some Successes:
I plugged in my little USB Z168A ADMtek
ADM8511 USB Fast Ethernet Adapter tiny network card and Puppy recognised it on the Asus P5GC-MX machine.

That's a bonus for putting Puppy on older machines with no network card
without opening the box.

My 1 Gig LG USB finally ran 2.17 Beta on another Asus cheapie unit.
But I had to change USB ports.
Always worked on different Gigabyte boards but not Asus.

Cheers for your great works...and also to the other happy Puppyites
who just keep giving their time, wit, patience, charm and brains to this
great Distro.

Chris.

PS: Added.
Saw this.

http://www.nabble.com/-PATCH--VIA-PCI-i ... 50480.html

" /* Asustek products */
product ASUSTEK HFCPCI 0x0675 ISDN

+/* Attansic Technology Corp. */
+product ATTANSIC ETHERNET_GIGA 0x1048 L1 Gigabit Ethernet Adapter
+product ATTANSIC ETHERNET_100 0x2048 L2 100 Mbit Ethernet Adapter
+ "

From this: Will it help or hinder?

" [PATCH] VIA PCI id updates + Attansic Technology addition
Click to flag this post

by Christoph Egger Jul 10, 2007; 12:54am :: Rate this Message: - Use ratings to moderate (?)

Reply | Reply to Author | View Threaded | Show Only this Message

Hi!

Patch is attached.

With the patch, dmesg still shows this:

# dmesg | grep product
pchb5: VIA Technologies product 0x6238 (rev. 0x00)
pciide0: Marvell product 0x6121 (rev. 0xb1)

Does anyone have an idea, what these products can be?
The Marvell one looks like to be a SATA controller.


Christoph

[pcidevs.diff]
Index: pcidevs
===================================================================
RCS file: /cvsroot/src/sys/dev/pci/pcidevs,v
retrieving revision 1.885
diff -u -p -r1.885 pcidevs
--- pcidevs 7 Jul 2007 20:30:47 -0000 1.885
+++ pcidevs 9 Jul 2007 14:47:25 -0000
@@ -600,6 +600,7 @@ vendor I4 0x17cf I4
vendor S2IO 0x17d5 S2io Technologies
vendor LINKSYS2 0x17fe Linksys
vendor RALINK 0x1814 Ralink Technologies
+vendor ATTANSIC 0x1969 Attansic Technologies
vendor SYMPHONY2 0x1c1c Symphony Labs (2nd PCI Vendor ID)
vendor TEKRAM2 0x1de1 Tekram Technology (2nd PCI Vendor ID)
vendor DATUM 0x12e2 Datum Inc. Bancomm-Timing Division
@@ -994,6 +995,10 @@ product ASIX AX88140A 0x1400 AX88140A 10
/* Asustek products */
product ASUSTEK HFCPCI 0x0675 ISDN

+/* Attansic Technology Corp. */
+product ATTANSIC ETHERNET_GIGA 0x1048 L1 Gigabit Ethernet Adapter
+product ATTANSIC ETHERNET_100 0x2048 L2 100 Mbit Ethernet Adapter
+
/* ATI products */
product ATI RADEON_RV380_3150 0x3150 Radeon Mobility X600 (M24) 3150
product ATI RADEON_RV380_3154 0x3154 FireGL M24 GL 3154
@@ -3580,6 +3585,7 @@ product V3 V96DPC 0xc960 V96DPC i960 (Du
product VIATECH VT6305 0x0130 VT6305 IEEE 1394 Host Controller
product VIATECH KT880 0x0269 KT880 CPU to PCI Bridge
product VIATECH VT8363_HB 0x0305 VT8363 (Apollo KT133) Host Bridge
+product VIATECH VT3351_HB_0351 0x0351 VT3351 Host Bridge
product VIATECH VT8371_HB 0x0391 VT8371 (Apollo KX133) Host Bridge
product VIATECH VT8501_MVP4 0x0501 VT8501 (Apollo MVP4) Host Bridge
product VIATECH VT82C505 0x0505 VT82C505 (Pluto)
@@ -3601,9 +3607,15 @@ product VIATECH VT86C926 0x0926 VT86C926
product VIATECH VT82C570M 0x1000 VT82C570M (Apollo) Host-PCI Bridge
product VIATECH VT82C570MV 0x1006 VT82C570M (Apollo) PCI-ISA Bridge
product VIATECH KT880_1 0x1269 KT880 CPU to PCI Bridge
+product VIATECH VT3351_HB_1351 0x1351 VT3351 Host Bridge
product VIATECH VT82C586_IDE 0x1571 VT82C586 IDE Controller
product VIATECH VT82C595_2 0x1595 VT82C595 (Apollo VP2) Host-PCI Bridge
product VIATECH KT880_2 0x2269 KT880 CPU to PCI Bridge
+product VIATECH VT3351_HB_2351 0x2351 VT3351 Host Bridge
+product VIATECH VT8251_PPB_287A 0x287a VT8251 PCI-PCI Bridge
+product VIATECH VT8251_PCIE1 0x287c VT8251 PCIE Root Port1
+product VIATECH VT8251_PCIE2 0x287d VT8251 PCIE Root Port2
+product VIATECH VT8251_VLINK 0x287e VT8251 Ultra VLINK Controller
product VIATECH VT83C572 0x3038 VT83C572 USB Controller
product VIATECH VT82C586_PWR 0x3040 VT82C586 Power Management Controller
product VIATECH VT3043 0x3043 VT3043 (Rhine) 10/100 Ethernet
@@ -3624,9 +3636,10 @@ product VIATECH VT8623_VGA 0x3122 VT8623
product VIATECH VT8623 0x3123 VT8623 (Apollo CLE266) CPU-PCI Bridge
product VIATECH VT8233A 0x3147 VT8233A PCI-ISA Bridge
product VIATECH VT8237_SATA 0x3149 VT8237 Integrated SATA Controller
+product VIATECH VT6421_RAID 0x3249 VT6421 Serial RAID Controller
product VIATECH VT3314_IG 0x3344 VT3314 CN900 UniChrome Integrated Graphics
product VIATECH VT8237R_SATA 0x3349 VT8237R Integrated SATA Controller
-product VIATECH VT6421_RAID 0x3249 VT6421 Serial RAID Controller
+product VIATECH VT3351_HB_3351 0x3351 VT3351 Host Bridge
product VIATECH KT880_3 0x3269 KT880 CPU to PCI bridge
product VIATECH VT8235 0x3177 VT8235 (Apollo KT400) PCI-ISA Bridge
product VIATECH VT8377 0x3189 VT8377 Apollo KT400 CPU to PCI Bridge
@@ -3634,10 +3647,16 @@ product VIATECH VT8378 0x3205 VT8378 Ap
product VIATECH VT8237 0x3227 VT8237 (Apollo KT600) PCI-ISA Bridge
product VIATECH VT8237A_HDA 0x3288 VT8237A/VT8251 High Definition Audio Controller
product VIATECH VT8237A_ISA 0x3337 VT8237A/VT82C586A PCI-ISA Bridge
+product VIATECH VT8237S_ISA 0x3372 VT8237S PCI-ISA Bridge
+product VIATECH VT8237A_PPB 0x337a VT8237A PCI-PCI Bridge
+product VIATECH VT8237A_HB 0x337b VT8237A Host Bridge
product VIATECH KT880_4 0x4269 KT880 CPU to PCI Bridge
+product VIATECH VT3351_HB_4351 0x4351 VT3351 Host Bridge
+product VIATECH VT3351_IOAPIC 0x5351 VT3351 I/O APIC Interrupt Controller
product VIATECH VT86C100A 0x6100 VT86C100A (Rhine-II) 10/100 Ethernet
product VIATECH VT8378_IG 0x7205 VT8378 KM400 UniChrome Integrated Graphics
product VIATECH KT880_5 0x7269 KT880 CPU to PCI Bridge
+product VIATECH VT3351_HB_7351 0x7351 VT3351 Host Bridge
product VIATECH VT8231 0x8231 VT8231 PCI-ISA Bridge
product VIATECH VT8231_PWR 0x8235 VT8231 Power Management Controller
product VIATECH VT8363_PPB 0x8305 VT8363 (Apollo KT133) PCI to AGP Bridge
@@ -3646,10 +3665,16 @@ product VIATECH VT8501AGP 0x8501 VT8501
product VIATECH VT82C597AGP 0x8597 VT82C597 (Apollo VP3) CPU-AGP Bridge
product VIATECH VT82C598AGP 0x8598 VT82C598 (Apollo MVP3) CPU-AGP Bridge
product VIATECH VT8605AGP 0x8605 VT8605 (Apollo ProMedia 133) Host-AGP Bridge
+product VIATECH K8T890_PPB_A238 0xa238 K8T890 PCI-PCI Bridge
product VIATECH VT8633AGP 0xb091 VT8633 (Apollo Pro 266) CPU-AGP Bridge
product VIATECH VT8366AGP 0xb099 VT8366 (Apollo KT266) CPU-AGP Bridge
product VIATECH VT8377AGP 0xb168 VT8377 CPU-AGP Bridge
product VIATECH VT8377CEAGP 0xb198 VT8377CE CPU-AGP Bridge
+product VIATECH VT3237_PPB 0xb999 K8T890 North / VT8237 South PCI-PCI Bridge
+product VIATECH K8T890_PPB_C238 0xc238 K8T890 PCI-PCI Bridge
+product VIATECH K8T890_PPB_D238 0xd238 K8T890 PCI-PCI Bridge
+product VIATECH K8T890_PPB_E238 0xe238 K8T890 PCI-PCI Bridge
+product VIATECH K8T890_PPB_F238 0xf238 K8T890 PCI-PCI Bridge

/* Vortex Computer Systems products */
product VORTEX GDT_60x0 0x0000 GDT6000/6020/6050 "

Also:
" Linux* Base Driver for the Attansic(R) L2 Fast Ethernet Adapter
==========================================================================

Contents
========

- In This Release
- Building and Installation
- Command Line Parameters
- Additional Configurations
- Known Issues
- Support

In This Release
===============

This file describes the Linux* Base Driver for the Attansic(R) L2 Fast
Ethernet Adapter, version 1.0.x. This driver supports the 2.4.x and 2.6.x kernels.

This driver is only supported as a loadable module at this time. Attansic is not
supplying patches against the kernel source to allow for static linking of
the driver. For questions related to hardware requirements, refer to the
documentation supplied with your Attansic(R) adapter. All hardware
requirements listed apply to use with Linux.

Building and Installation
=========================

To build a binary RPM* package of this driver, run 'rpmbuild -tb
<filename.tar.gz>'. Replace <filename.tar.gz> with the specific filename of
the driver.

NOTE: For the build to work properly, the currently running kernel MUST match
the version and configuration of the installed kernel sources. If you
have just recompiled the kernel reboot the system now.

RPM functionality has only been tested in Red Hat distributions.

1. Move the base driver tar file to the directory of your choice. For example,
use /home/username/atl2 or /usr/local/src/atl2.

2. Untar/unzip archive:

tar zxf atl2-x.x.x.tar.gz

3. Change to the driver src directory:

cd atl2-x.x.x/src/

4. Compile the driver module:

make install

The binary will be installed as:

/lib/modules/<KERNEL VERSION>/kernel/drivers/net/atl2.[k]o

The install locations listed above are the default locations. They might
not be correct for certain Linux distributions. For more information,
see the ldistrib.txt file included in the driver tar.

5. Install the module:

insmod atl2 <parameter>=<value>

6. Assign an IP address to the interface by entering the following, where
x is the interface number:

ifconfig ethx <IP_address>

7. Verify that the interface works. Enter the following, where <IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:

ping <IP_address>

Command Line Parameters
=======================

If the driver is built as a module, the following optional parameters are
used by entering them on the command line with the modprobe or insmod command
using this syntax:

modprobe atl2 [<option>=<VAL1>,<VAL2>,...]

insmod atl2 [<option>=<VAL1>,<VAL2>,...]

For example, with two L001 PCIE adapters, entering:

insmod atl2 TxMemSize=80,128
loads the atl2 driver with 8KB TX memory for the first adapter and 10KB TX memory
for the second adapter.

The default value for each parameter is generally the recommended setting,
unless otherwise noted.

NOTES: A descriptor describes a data buffer and attributes related to the
data buffer. This information is accessed by the hardware.

MediaType
Valid Range: 0-4
0 - auto-negotiate at all supported speeds
1 - only link at 100Mbps Full Duplex
2 - only link at 100Mbps Half Duplex
3 - only link at 10Mbps Full Duplex
4 - only link at 10Mbps Half Duplex
Default Value: 0
MediaType forces the line speed/duplex to the specified value in
megabits per second(Mbps). If this parameter is not specified or is set
to 0 and the link partner is set to auto-negotiate, the board will
auto-detect the correct speed.

IntModTimer
Valid Range: 50-65000
Default Value: 100
This value represents the minmum interval between interrupts controller
generated.

RxMemBlock
Valid Range: 16-512
Default Value: 64
This value is the number of receice memory block allocated by the driver.
Increasing this value allows the driver to buffer more incoming packets.
Each memory block is 1536 bytes.

NOTE: Depending on the available system resources, the request for a
higher number of receive descriptors may be denied. In this case,
use a lower number.

TxMemSize
Valid Range: 4-64
Default Value: 8
This value is the number KB of transmit memory allocated by the driver.
Increasing this value allows the driver to queue more transmits.

NOTE: Depending on the available system resources, the request for a
higher number of transmit descriptors may be denied. In this case,
use a lower number.

FlashVendor
Valid Range: 0-2
Default Value: 0
This value standards on vendor of spi flash used by the adapter.
0 for Atmel, 1 for SST, 2 for ST


Additional Configurations
=========================

Configuring the Driver on Different Distributions
-------------------------------------------------

Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding
an alias line to /etc/modules.conf as well as editing other system startup
scripts and/or configuration files. Many popular Linux distributions ship
with tools to make these changes for you. To learn the proper way to
configure a network device for your system, refer to your distribution
documentation. If during this process you are asked for the driver or module
name, the name for the Linux Base Driver for the Attansic L2 is atl2

As an example, if you install the atl2 driver for two L2 adapters
(eth0 and eth1) and set the speed and duplex to 10full and 100half, add the
following to modules.conf:

alias eth0 atl2
alias eth1 atl2
options atl2 Speed=10,100 Duplex=2,1

Viewing Link Messages
---------------------

Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages
on your console, set dmesg to eight by entering the following:

dmesg -n 8

NOTE: This setting is not saved across reboots.


Known Issues
============

NOTE: For distribution-specific information, see the ldistrib.txt file
included in the driver tar.

Driver Compilation
------------------

When trying to compile the driver by running make install, the following
error may occur:

"Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source
tree and entering:

make include/linux/version.h.


Support
=======

For general information, go to the Attansic support website at:

http://support.attansic.com

If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to
the issue to xiong_huang@attansic.com

License
=======

This software program is released under the terms of a license agreement
between you ('Licensee') and Attansic. Do not use or load this software or any
associated materials (collectively, the 'Software') until you have carefully
read the full terms and conditions of the LICENSE located in this software
package. By loading or using the Software, you agree to the terms of this
Agreement. If you do not agree with the terms of this Agreement, do not
install or use the Software.

* Other names and brands may be claimed as the property of others. "

If this posting is too long please edit or PM me to edit...Chris

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#44 Post by PaulBx1 »

A tiny (but easy to fix) item: when you run Partview, the window is positioned too low so it ends up behind the task bar. Been that way forever...

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#45 Post by PaulBx1 »

Want to report another success: I used the universal installer to put puppy on my PQI flash drive, and my pupsave, and booted properly off my USB 1.1 bus (a bit slow, but doable). This was something I gave up on a couple of revisions back because I never could get it to work. So that is very cool! 8) Weird to boot a computer without the hard drive chattering away...

Only non-standard thing I did was that I used John Doe's latest wakepup2 found here:
http://www.murga-linux.com/puppy/viewto ... 924#122924
because I needed the USB 1.1 support. I don't think 2.17B has that yet? Please put it in 2.17 if you can...

Two minor bobbles in the process. The dd to load the wakepup didn't work until I did a low-level format of the floppy. And I got the "It seems that the last time X ran..." message when I booted, which was strange because the last time I shut down I thought it came down properly. I guess that is /etc/.XLOADED.

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#46 Post by John Doe »

PaulBx1 wrote:I don't think 2.17B has that yet? Please put it in 2.17 if you can...
Barry had the latest version that I had posted at the time of the 2.17b release. I'm guessing he'll drop the latest (that I just posted an hour ago) in the final.

in fact it's still at 0 downloads. paul, if you wanted to grab the latest and give a try that would be cool. i fine tuned a few things and dropped that loglevel option in there for custom boots.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#47 Post by PaulBx1 »

I can try it. I posted my experience about it on that thread of yours. BTW you need to fix your example "dd" command in that post by removing the "/"...

One thing there that looked like it might be a problem not with wakepup2 but with the init script in /initrd, is that I can boot using flash from my computer's USB 1.1 port, but not from the 2.0 port on my pcmcia card. It hangs on the "Loading kernel modules..." step.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#48 Post by jamesbond »

test on nforce 405:
1. boot - ok
2. sound - ok
3. video - needs editing. Choosing xorg at startup causes failure to go to GUI. Checked xorg.conf, xorgwizard choose "nvidia" driver - which does not exist. Changed that to "nv", still not working. Changed that to "vesa" - and we have a go.
4. gxine DVD playback - ok
5. wired onboard network - ok (using forcedeth)
6. test with linksys wusb54g - the rt73 based usb wifi. Manually load the driver from network wizard (I plugged the stick after puppy was up and running), got the wlan0 interface, but WPA setup always fails. Running wpa_supplicant directly from terminal gives me this error message:

Code: Select all

ioctl[SIOCSIWPMKSA]: Network is down
ioctl[SIOCSIWMODE]: Network is down
Could not configure driver to use managed mode
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Trying to associate with SSID 'jbnet'
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 6 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWGENIE]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 0 value 0x2 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 1 value 0x4 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 2 value 0x4 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 3 value 0x2 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 10 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 8 value 0x0 - Association request to the driver failed
7. printer - not tested, I know it's a tough one to setup (pixma MP 1500)
8. I have softmodem but it's not detected. Cant' tell you much since lspci also doesn't list it --- there are a few unknown devices there.

(3) is a known problem - it happened in 2.16 at least (and probably earlier version as well).
(6) is also a known problem (from 2.13 days), in the past this forced me to use ndiswrapper. I thought this http://murga-linux.com/puppy/viewtopic. ... =468853927has been merged with 2.17beta and would have solved it? I also tried this (trying to load the wlan_* modules manually)http://murga-linux.com/puppy/viewtopic. ... 6&start=15 with no success
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#49 Post by tempestuous »

jamesbond,
Puppy 2.17 contains the very latest rt73 module compiled from CVS source. This new rt73 now creates an interface called "wlan0", where it previously created an interface called "rausb0", and maybe this has broken compatibility with wpa_supplicant.
Can you confirm that the command you ran was this -

wpa_supplicant -i wlan0 -D ralink -c /etc/wpa_supplicant.conf -dd

User avatar
jcoder24
Posts: 604
Joined: Fri 06 May 2005, 12:33
Location: Barbados

Two requests for 2.17 final

#50 Post by jcoder24 »

Having either of these implemented would be greatly appreciated.

1) Xrun command line be moved from menu->utilities->Xrun to menu->Xrun

I prefer to just type a command in the run dialog that having to search/nahttp://www.murga-linux.com/puppy/images/icons/icon17.gifvigate the menu. Having to go all the way up to Utilities and then all the way down to Xrun is a bit too much for the frequency of use it gets IMO.

2) Show desktop button. This is for the one or two items that I use frequently that I have on the desktop.

User avatar
willhunt
Posts: 495
Joined: Wed 05 Oct 2005, 18:19

heavy encryption

#51 Post by willhunt »

the heavy encryption is working great for me and really does not bog on me I love it now me and pinky can finish our plans for world conquest!
[url=http://hostfile.org/icepak.pet]176 Icewm Themes :!:[/url]
[url=http://tinyurl.com/39fl3x]vlc-0.8.6c-i586.pet[/url]
[url=http://tinyurl.com/2q7cbp]vlc-0.8.6c-i586.pet[/url]

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#52 Post by jamesbond »

tempestuous wrote:jamesbond,
Puppy 2.17 contains the very latest rt73 module compiled from CVS source. This new rt73 now creates an interface called "wlan0", where it previously created an interface called "rausb0", and maybe this has broken compatibility with wpa_supplicant.
Can you confirm that the command you ran was this -

wpa_supplicant -i wlan0 -D ralink -c /etc/wpa_supplicant.conf -dd
The command used by both network wizard (took a peek with ps-aef) and myself was using -D wext. I will try again with -D ralink tonight.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#53 Post by kirk »

Mr. Bond,
ioctl[SIOCSIWPMKSA]: Network is down
Might want to try doing a "ifconfig wlan0 up" too.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#54 Post by PaulBx1 »

I was trying the new wakepup2 in this thread:

http://www.murga-linux.com/puppy/viewto ... 1&start=15

The flash drive was plugged into a usb 2.0 port on a pcmcia card. I hang in the step "USB-Storage: Detecting connected device(s)..."

That is in the function usbstoragecompletionfunc. If I read that loop right it should grep from dmesg every second, and if it does not find every device it waits, printing out an incrementing $SLPCNT every second. I never see that printed out.

Maybe that "continue" statement is being executed, which would short-circuit any printing, and also any possibility of a timeout. Anyway apparently it can't see the flash on a pcmcia card. I wonder if wakepup2 should be using another boot parameter, like one for pcmcia? I can boot the flash off the laptop's default USB 1.1 port.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#55 Post by jamesbond »

jamesbond wrote:
tempestuous wrote:jamesbond,
Puppy 2.17 contains the very latest rt73 module compiled from CVS source. This new rt73 now creates an interface called "wlan0", where it previously created an interface called "rausb0", and maybe this has broken compatibility with wpa_supplicant.
Can you confirm that the command you ran was this -

wpa_supplicant -i wlan0 -D ralink -c /etc/wpa_supplicant.conf -dd
The command used by both network wizard (took a peek with ps-aef) and myself was using -D wext. I will try again with -D ralink tonight.
That does it. -D ralink is the charms - it works straight away. I can confirm however, that network wizard still try to run it with -D wext instead. I'm posting this with my rt73 now.
Kirk, thanks, I tried - running "ifconfig wlan0 up" doesn't make any difference.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#56 Post by tempestuous »

jamesbond wrote:I can confirm however, that network wizard still try to run it with -D wext
OK, thanks for reporting.
Obviously wpa_supplicant is fine, it's the Wizard which can't deal with the rt73's new "wlan0" interface name.
I will pass this on to Dougal, who is currently revising and improving the Wizard.

kirk, I just came across your post here -
http://www.murga-linux.com/puppy/viewto ... 059#119059
which talks about making wifi setup more reliable by splitting the iwconfig parameters into separate commands.
While we're refining the Wizard, I think we should adopt this technique.
Also you talk about "open" versus "restricted" WEP authentication, which is obviously an important setting, so we need to add this option to the Wizard.
In your opinion, which should be the default WEP setting in the Wizard, open or restricted?

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#57 Post by John Doe »

tempestuous wrote:...which talks about making wifi setup more reliable by splitting the iwconfig parameters into separate commands.
While we're refining the Wizard, I think we should adopt this technique.
I've mentioned that before also and concur that it seems to work better.

Even to the point of being required on one of my cards.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#58 Post by PaulBx1 »

OK, I looked at what might be causing the hang I was experiencing when booting my flash drive from a pcmcia card USB 2.0 port, and decided the way the code is written in usbstoragecompletionfunc of the init script could cause an infinite loop. So, I rearranged the code to look like this (sorry for the line wrap):

Code: Select all

#v2.10 jesse... v2.17 PaulBx1 rearranged to eliminate endless loop
usbstoragecompletionfunc() {
 WAITUSB=""
 if [ ! "`lsmod | grep "^usb_storage"`" = "" ];then #precaution.
  echo -n "USB-Storage: Detecting connected device(s)..."
  SLPCNT=0;USBSTORAGES=0;AVAILABLEUSBSTORAGES=0
  while true;do
   sleep 1  
   SLPCNT=`expr $SLPCNT + 1`
   echo -n " $SLPCNT"
   if [ $SLPCNT -gt $TIMEOUTUSB ]; then
    echo
    echo "USB-Storage: Device scan time-out $SLPCNT secs, found $AVAILABLEUSBSTORAGES of $USBSTORAGES device(s)."
    break
   fi
   #v2.15 busybox 1.4.1 grep not accept -o option....
   #USBSTORAGES=`/bin/dmesg | grep -o "usb-storage: device found at.*" | wc -l | sed -e 's/ //g'`
   USBSTORAGES=`/bin/dmesg | grep "usb-storage: device found at" | wc -l | sed -e 's/ //g'`
   AVAILABLEUSBSTORAGES=`/bin/dmesg | grep "usb-storage: device scan complete" | wc -l | sed -e 's/ //g'`
   if [ $USBSTORAGES -eq $AVAILABLEUSBSTORAGES ]; then
    #v2.10r1 booting from usb...
    if [ ! "`echo -n "$PMEDIA" | grep "usb"`" = "" ];then
     if [ $AVAILABLEUSBSTORAGES -eq 0 ];then #0 not acceptable
      continue
     fi
    fi
    echo
    echo "USB-Storage: Device scan complete for all $AVAILABLEUSBSTORAGES devices"
    break
   fi
  done
 fi
} #end usbstoragecompletionfunc
I believe this will make it timeout one second earlier, so at the places where this is called, maybe the timeout should be bumped by one second.

Anyway I tried to build a new initrd and put it on a new CD. However when I boot it I get the message "Bummer, cannot run /etc/init.d/rcS, no such file or directory". :? I'm guessing that the edit-initrd rox application that was put together a few revisions back does not work any more, or something like that. Anyway I have not been able to test this code. If someone wants to give me a new initrd for the 2.17B iso, I will test it and see if it times out as expected, rather than sitting in an endless loop.

Jesse
Posts: 466
Joined: Sun 08 May 2005, 16:07
Location: Auckland, NZ

#59 Post by Jesse »

Hello,

I've just tried out the Puppy 2.17beta, on a multisession CD, just to try things out, and I have noticed what seems to be a problem.
I run the network wizard and setup networking ok.
I run the ALSA wizard and select the usb-sound module, and sound works, but this setting is not kept through a reboot, where I saved the session, even though the networking option was kept.

The motherboard has a c-media audio card on it, but no speakers attached, perhaps there is a conflict? or the c-media overrides the usb-audio for some reason?

Jesse

Post Reply