Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 24 Oct 2014, 07:34
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Puppy 4 DINGO
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 6 of 17 [248 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 15, 16, 17 Next
Author Message
rokky

Joined: 20 Jan 2008
Posts: 8

PostPosted: Sun 04 May 2008, 22:32    Post subject: Missing ACX Wifi Module  

BarryK wrote:
tempestuous wrote:
BarryK wrote:
One of the contributors to the Network Wizard has put that code in that puts up a message about WPA not being supported

Yes, that was Dougal and me.
Whether the Network Wizard should warn about modules not supporting WPA is up for discussion (I think it should), but the wag-profiles.sh script definitely must be updated whenever new wifi modules are introduced - because wpa_supplicant needs a different "-D" (driver) parameter depending on what module is in use.
You will notice that the WPA section of the wag-profiles.sh script not only defines the modules which are WPA-compatible, but more importantly it specifies what "-D" parameter to pass to wpa_supplicant. The modules and "D" parameters that are currently listed in the wag-profiles script are absolutely correct thus far ... but of course, recent kernels now provide some new wifi kernel modules which must be incorporated.

How to know what -D parameter applies to each wifi module? Careful reading of the wpa_supplicant README and also the documentation provided with the source code of each wifi driver. I discussed this at length with rarsa when he first wrote the Network Wizard. Since then, I have helped Dougal add rt61/rt73 (Ralink) and r8180/r8187 (Realtek). We also added WPA2 support, which requires a significantly different configuration file for wpa_supplicant.

I just downloaded Puppy-4.00-k2.6.25 to have a look at the new wifi modules.
These are the new modules which need to be added to the Wizard:
D parameter "wext" -
ath5k
b43
b43legacy
iwl3945
iwl4965
rndis_wlan (Broadcom USB)
rt61pci
rt73usb

D parameter "ipw" -
rtl8180
rtl8187

Notice that the new rt61pci and rt73usb modules use the "wext" D parameter, whereas the old rt61 and rt73 modules use the "ralink" D parameter. This is because the new modules are from a completely revised development stream; the "next-generation" rt2x00 series.

I cannot guarantee that the new driver parameters I have specified are completely correct. I do not own all of these devices, and the information is difficult to glean from the web. Testing may prove me wrong on some of these.

tempestuous,
Thanks very much for figuring that out. I didn't have a clue how to do that, but really wanted it done for 4.00final. I've added the extra modules in the appropriate places in the wag-profiles.sh script.


I did not see the ACX module for my Hawking 54g card, which I am using right now to post this from Puppy 3.01, so I know it can be done.

Interesting, too that the no WPA support message would pop up when the wifi card is not even detected/known...

rokky
Back to top
View user's profile Send private message 
rokky

Joined: 20 Jan 2008
Posts: 8

PostPosted: Sun 04 May 2008, 22:32    Post subject: Missing ACX Wifi Module  

BarryK wrote:
tempestuous wrote:
BarryK wrote:
One of the contributors to the Network Wizard has put that code in that puts up a message about WPA not being supported

Yes, that was Dougal and me.
Whether the Network Wizard should warn about modules not supporting WPA is up for discussion (I think it should), but the wag-profiles.sh script definitely must be updated whenever new wifi modules are introduced - because wpa_supplicant needs a different "-D" (driver) parameter depending on what module is in use.
You will notice that the WPA section of the wag-profiles.sh script not only defines the modules which are WPA-compatible, but more importantly it specifies what "-D" parameter to pass to wpa_supplicant. The modules and "D" parameters that are currently listed in the wag-profiles script are absolutely correct thus far ... but of course, recent kernels now provide some new wifi kernel modules which must be incorporated.

How to know what -D parameter applies to each wifi module? Careful reading of the wpa_supplicant README and also the documentation provided with the source code of each wifi driver. I discussed this at length with rarsa when he first wrote the Network Wizard. Since then, I have helped Dougal add rt61/rt73 (Ralink) and r8180/r8187 (Realtek). We also added WPA2 support, which requires a significantly different configuration file for wpa_supplicant.

I just downloaded Puppy-4.00-k2.6.25 to have a look at the new wifi modules.
These are the new modules which need to be added to the Wizard:
D parameter "wext" -
ath5k
b43
b43legacy
iwl3945
iwl4965
rndis_wlan (Broadcom USB)
rt61pci
rt73usb

D parameter "ipw" -
rtl8180
rtl8187

Notice that the new rt61pci and rt73usb modules use the "wext" D parameter, whereas the old rt61 and rt73 modules use the "ralink" D parameter. This is because the new modules are from a completely revised development stream; the "next-generation" rt2x00 series.

I cannot guarantee that the new driver parameters I have specified are completely correct. I do not own all of these devices, and the information is difficult to glean from the web. Testing may prove me wrong on some of these.

tempestuous,
Thanks very much for figuring that out. I didn't have a clue how to do that, but really wanted it done for 4.00final. I've added the extra modules in the appropriate places in the wag-profiles.sh script.


I did not see the ACX module for my Hawking 54g card, which I am using right now to post this from Puppy 3.01, so I know it can be done.

Interesting, too that the no WPA support message would pop up when the wifi card is not even detected/known...

rokky
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Sun 04 May 2008, 23:43    Post subject: Re: Missing ACX Wifi Module  

rokky wrote:
I did not see the ACX module for my Hawking 54g card, which I am using right now to post this from Puppy 3.01, so I know it can be done.

Yes, Barry has not provided the acx100 drivers for Puppy-4.0. I suggest you wait for Puppy-4.1 when the 2.6.25 kernel is due for a slight upgrade.

rokky wrote:
Interesting, too that the no WPA support message would pop up when the wifi card is not even detected/known...

The WPA warning only appears when the user selects "WPA" or "WPA2" encryption, and a non-WPA-supported wifi module has been selected.
Back to top
View user's profile Send private message 
ralphv

Joined: 17 Mar 2007
Posts: 41

PostPosted: Mon 05 May 2008, 00:03    Post subject:  

Pidgin in 4.00 final isn't pm-ing. Xchat can do it, though

Ralph
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Mon 05 May 2008, 03:03    Post subject:  

ralphv wrote:
Pidgin in 4.00 final isn't pm-ing. Xchat can do it, though

Ralph

What! That's the very latest Pidgin in Dingo! Along with all its bloat ...I reluctantly left out the much slimmer Ayttm.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
urban soul


Joined: 05 Mar 2008
Posts: 276
Location: "Killing a nerd is not as much fun as ist sounds" B.Simpson

PostPosted: Mon 05 May 2008, 04:02    Post subject:
Subject description: WPA support
 

tempestuous wrote:

rokky wrote:
Interesting, too that the no WPA support message would pop up when the wifi card is not even detected/known...

The WPA warning only appears when the user selects "WPA" or "WPA2" encryption, and a non-WPA-supported wifi module has been selected.

Hello tempestuous,

thank you for the input on the -D param for wpa_supplicant in your previous post!
The warning pops up when wag-profiles.sh is run and the command
`readlink /sys/class/net/$INTERFACE/device/driver`
does not return one of these:
'hostap | rt61 | rt73 | rt2500 | bcm43xx | ipw2100 | ipw2200 | ipw3945 | r8180 | r8187 '

This is also true if no driver was loaded or the interface is unknown to puppy.

Additionaly the WPA fields are disabled. The list above is beeing updated for the final release if I understood right.
If we need a database for the wireless drivers how about putting it in a separate file (with an update function) ? /etc/networkmodules could be used e.g.

Urban

Edit: in Dingo 4.00 final puppy knows about these drivers supporting WPA:

Quote:
hostap
rt61|rt73
bcm43xx|ipw2100|ipw2200|ipw3945|ath_pci
ndiswrapper
zd1211|zd1211b|zd1211rw|ath5k|b43|b43legacy
iwl3945|iwl4965|rndis_wlan|rt61pci|rt73usb
r8180|r8187|rtl8180|rtl8187


hope this is of interest for regular users.
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Mon 05 May 2008, 06:40    Post subject:
Subject description: WPA support
 

Urban, you have raised two separate issues:
urban soul wrote:
If we need a database for the wireless drivers how about putting it in a separate file (with an update function) ?

That's for Barry and/or rarsa and/or Dougal to decide. I just contributed some configuration details. Scripting was done by rarsa, then modified by Dougal for additional features.

urban soul wrote:
The warning pops up when wag-profiles.sh is run and the command
`readlink /sys/class/net/$INTERFACE/device/driver`
does not return one of these:
'hostap | rt61 | rt73 | rt2500 | bcm43xx | ipw2100 | ipw2200 | ipw3945 | r8180 | r8187 '

This is also true if no driver was loaded or the interface is unknown to puppy.

I was about to suggest that the WPA warning in this instance is erroneous and should be corrected ... but then, I don't really see a fault. If no interface is selected, then certainly WPA is not possible! Maybe it's just the wording of the warning that needs to be changed?
Or if we look deeper, I'm wondering whether the fault is further back in the chain? Perhaps the Wizard should not even allow a user to get to the wifi configuration gui if no module is selected?
Again, ultimately this is not my decision. Feel free to move this information to a new thread in "Suggestions".

Personally, I would like to see Pwifiscan (or whatever it's called) integrated into the Network Wizard.
Back to top
View user's profile Send private message 
NathanO

Joined: 22 Feb 2007
Posts: 198
Location: San Antonio, TX

PostPosted: Mon 05 May 2008, 11:19    Post subject:  

Follow up on HP Pavilion zv6000 per Barry's request.

Cold Boot
.25 Kernel lsmod:
usbhid 31616 0

I will have to hand copy the devices file with spaces as on the laptop screen:

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 pd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sun=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 2.06
S: Manufacturer=Linux 2.6.25 ehic_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:13.2
C:* #Ifs= 1 Cfg#= 1 Atr=e) MxPwr= 0mA
I:* If#= 0 Alt=0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

Cold Boot
.21 Kernel lsmod:
usbhid 24928 0

Copy of device:

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.21.7 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:13.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 4
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.21.7 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:13.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 4
B: Alloc= 14/900 us ( 2%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.21.7 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:13.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=1241 ProdID=1166 Rev= 2.70
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms

Anything else you need?
Back to top
View user's profile Send private message 
vito

Joined: 14 Sep 2006
Posts: 54
Location: US

PostPosted: Mon 05 May 2008, 12:03    Post subject: Dingo final w/.21.7 kernel
Subject description: non-syncing filesystem
 

Hello All,

I booted up dingo final and installed it fresh full/wipe drive.
When I try to reboot I get an error that kernel panic filesystem not syncing, can't mount VFS and then something from grub perhaps about block device (0,0) which is the correct hard drive and partition where puppy and grub were installed.

The puppy .25 kernel version worked fine and all previous versions of Puppy, but not dingo final release .21.7 kernel version. I do not wish to use the .25 version because the wireless setup in the network wizard has new drivers that don't work with my dlink wireless pci card., the old ath0 driver in the dingo release candidates worked fine.

Thats my sad but true story.

Mny Thx,
Vito
AMD 750 box with 356 mb memory
Back to top
View user's profile Send private message 
veronicathecow


Joined: 21 Oct 2006
Posts: 533

PostPosted: Mon 05 May 2008, 12:17    Post subject:  

Hi Barry.
Just tried Final of 4.0 and get same result as the SC version

2.6.25 Kernel, MD5 sum correct. disk verified on blowing. Intel D201GLY2 MB

Stops at booting linux kernel.

Previous version of 4 with later kernel have worked so not sure what has changed.

This CD works fine on an older Athlon.
Cheers
Tony
Back to top
View user's profile Send private message 
Caneri

Joined: 04 Sep 2007
Posts: 1580
Location: Canada

PostPosted: Mon 05 May 2008, 12:18    Post subject:  

Hi Lobster et al,

Dingo4 Final is ready here

http://www.puppylinux.ca/puppyfiles/puppy-4.00-k2.6.21.7-seamonkey.iso
http://www.puppylinux.ca/puppyfiles/puppy-4.00-k2.6.21.7-seamonkey.iso.md5.txt

The unleashed and devx will come soon....
Best,
Eric

_________________
Be not afraid to grow slowly, only be afraid of standing still.
Chinese Proverb

Back to top
View user's profile Send private message 
tronkel


Joined: 30 Sep 2005
Posts: 1101
Location: Vienna Austria

PostPosted: Mon 05 May 2008, 12:30    Post subject:  

Just been taking Dingo for a test drive - and very nice it is.

I noticed an uninvited guest in the CUPS printers screen - a printer (Brother model) there. Since I have never owned one of these models, it must belong to Barry. Must have crept in to the ISO via a CUPS configuration file somewhere.

_________________
Life is too short to spend it in front of a computer
Back to top
View user's profile Send private message Visit poster's website AIM Address 
alcy

Joined: 04 May 2008
Posts: 144

PostPosted: Mon 05 May 2008, 12:33    Post subject:  

The Xorg.conf file could've been edited and the tap option (for laptop touchpads) already set by default, as not doing this could turn away people (as rightly pointed by alienjeff in the other thread. ) How about doing that in upgraded version ?
The other thread : http://www.murga-linux.com/puppy/viewtopic.php?t=28724
Back to top
View user's profile Send private message 
barriew

Joined: 17 Oct 2006
Posts: 88
Location: Essex, UK

PostPosted: Mon 05 May 2008, 14:27    Post subject: USB mouse in 2.6.25 FINAL  

Hi - an interesting event in the final on the latest kernel. The original boot from CD takes a very long time - at least 3 times the .21 kernel version, and fails to detect the USB mouse, HOWEVER, after a full HD install and reboot, the mouse is working Very Happy I noticed this in the SC version also.

This version seems rather better with my ZD1211rw wireless dongle. Network Wizard still fails to set it up, but Pwireless has no problems.

Barrie
Back to top
View user's profile Send private message 
alcy

Joined: 04 May 2008
Posts: 144

PostPosted: Mon 05 May 2008, 15:10    Post subject:  

Also, on my baby laptop, the rxvt terminal display is frequently messed up :
rxvtscrn.png
 Description   rxvt screenshot
 Filesize   13.88 KB
 Viewed   788 Time(s)

rxvtscrn.png

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 6 of 17 [248 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 15, 16, 17 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1212s ][ Queries: 12 (0.0119s) ][ GZIP on ]