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 Tue 21 May 2013, 09:43
All times are UTC - 4

 Forum index » House Training » Bugs ( Submit bugs )
Trouble getting PCMCIA slot recognized in a recent Puppy?
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [14 Posts]  
Author Message
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6856
Location: Perth, Western Australia
PostPosted: Tue 10 May 2011, 09:41    Post subject:  Trouble getting PCMCIA slot recognized in a recent Puppy?
Subject description: See this		  
I need assistance from someone who has experienced trouble with getting their PCMCIA slot to be recognized with a recent Puppy, but who did have it recognized with an older Puppy (say 4.3.1).

See my blog post for test questions:

http://bkhome.org/blog/?viewDetailed=02274

Please note that my request is for recognition of the slot itself, not whatever card is plugged in. They are actually two different issues.
_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send private message Visit poster's website 
Keef


Joined: 20 Dec 2007
Posts: 428
Location: Staffordshire
PostPosted: Tue 10 May 2011, 17:21    Post subject:  
Read the blog first and wrote this up - not sure its what you want now, but here it is anyway. (Can't mount CF card in adapter on the recent pups without the edit).

Quirky 421
Compaq Armada M700 PIII 450

Booted clean frugal install (pfix=ram):

#pcmcia-socket-startup

/sys/class/pcmcia_socket/
pcmcia_socket0
pcmcia_socket1

Output of elspci -l
01:00.0 030000 1002:4C4D <>
00:09.1 070000 11C1:0445 <ltmodem>
00:09.0 020000 8086:1229 <e100>
00:08.0 040100 125D:1978 <>
00:07.3 068000 8086:7113 <piix4_smbus>
00:07.2 0C0300 8086:7112 <uhci_hcd>
00:07.1 010180 8086:7111 <ata_piix>
00:07.0 068000 8086:7110 <>
00:04.1 060700 104C:AC1B <yenta_cardbus>
00:04.0 060700 104C:AC1B <yenta_cardbus>
00:01.0 060400 8086:7191 <>
00:00.0 060000 8086:7190 <agpgart-intel>

---------------
Uncomment following line, save & reboot:
pcmcia-socket-startup

/sys/class/pcmcia_socket/
pcmcia_socket0
pcmcia_socket1

Output of elspci -l
01:00.0 030000 1002:4C4D <>
00:09.1 070000 11C1:0445 <ltmodem>
00:09.0 020000 8086:1229 <e100>
00:08.0 040100 125D:1978 <ES1968 (ESS Maestro)>
00:07.3 068000 8086:7113 <piix4_smbus>
00:07.2 0C0300 8086:7112 <uhci_hcd>
00:07.1 010180 8086:7111 <ata_piix>
00:07.0 068000 8086:7110 <>
00:04.1 060700 104C:AC1B <yenta_cardbus>
00:04.0 060700 104C:AC1B <yenta_cardbus>
00:01.0 060400 8086:7191 <>
00:00.0 060000 8086:7190 <agpgart-intel>
--------------------------------------------------------
Hardinfo report (in case its useful):
PCI Devices
Host bridge Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
PCI bridge Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
CardBus bridge Texas Instruments PCI1450
CardBus bridge Texas Instruments PCI1450
Bridge Intel Corporation 82371AB/EB/MB PIIX4 ISA
IDE interface Intel Corporation 82371AB/EB/MB PIIX4 IDE
USB Controller Intel Corporation 82371AB/EB/MB PIIX4 USB
Bridge Intel Corporation 82371AB/EB/MB PIIX4 ACPI
Multimedia audio controller ESS Technology ES1978 Maestro 2E
Ethernet controller Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
Serial controller Agere Systems LT WinModem
VGA compatible controller ATI Technologies Inc Rage Mobility P/M AGP 2x
Back to top
View user's profile Send private message 
vickyg2003


Joined: 29 Apr 2011
Posts: 64
PostPosted: Tue 10 May 2011, 20:07    Post subject:  
Answer from Lucid Puppy 5.2.5

Quote:
Question 1
Then look in /sys/class, do you see pcmcia_socket/pcmcia_socket0?

Yes both 0 and 1

(Do you think its those of us with 2 pcmcia slots that are problematic)



Quote:
Question 2
Run this in a terminal:
# elspci -l
(that is letter l on the end)
You should see a line with <yenta_socket> on it, can you please post that entire line here or the forum.



EDIT:
Better yet, send the entire output from running "elspci -l" (highlight text in terminal by holding left-mouse-button down and drag, then click the middle-mouse-button to paste)

no I don't see the socket. However I don't have a middle button on my mouse (new mouse is on order) so have attached screen shot.


Quote:

Question 3
Then, if you uncomment uncomment line 16 in /etc/init.d/rc.pcmcia:
pcmcia-socket-startup

then reboot, look again in /sys/class, do you get pcmcia_socket?



If I uncomment that line an reboot card is recognized and orinco_cs is selected.
forbarry.png
 Description   Picture of elspci -l
 Filesize   360.79 KB
 Viewed   373 Time(s)

forbarry.png
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6856
Location: Perth, Western Australia
PostPosted: Tue 10 May 2011, 20:10    Post subject:  
I think that I know how to fix the problem....

Keef,
If I could trouble you to do one more thing. Comment-out that "pcmcia-socket-startup" line, then reboot.

So, you now have a non-functioning PCMCIA slot.

Open a terminal and type this:

Code:
# udevadm trigger --subsystem-match="pcmcia*"


wait a few seconds, then... is your PCMCIA card now recognised? -- running "elspci -l", you should see the line with "ESS Maestro" in it.
_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6856
Location: Perth, Western Australia
PostPosted: Tue 10 May 2011, 20:13    Post subject:  
vivkyg2003,
Thanks for responding, your post overlapped my previous one.

Would you mind also trying that thing with "udevadm"?

A note on "mice", yeah the middle button is most helpful with Linux, it pastes currently-highlighted text.

Most scroll-wheel mice also support the middle button -- my Logitech scrollwheel mouse, the scrollwheel can be clicked by pressing on it, so is also a middle button.
Back to top
View user's profile Send private message Visit poster's website 
vickyg2003


Joined: 29 Apr 2011
Posts: 64
PostPosted: Tue 10 May 2011, 20:51    Post subject:  
BarryK wrote:
I think that I know how to fix the problem....

If I could trouble you to do one more thing. Comment-out that "pcmcia-socket-startup" line, then reboot.

So, you now have a non-functioning PCMCIA slot.

Open a terminal and type this:

Code:
# udevadm trigger --subsystem-match="pcmcia*"


wait a few seconds, then... is your PCMCIA card now recognised? -- running

Yes it started blinking within a second.

Quote:

"elspci -l", you should see the line with "ESS Maestro" in it.

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


Joined: 09 May 2005
Posts: 6856
Location: Perth, Western Australia
PostPosted: Tue 10 May 2011, 22:41    Post subject:  
That "ESS Maestro" was a reply to Keef, he/she has a ESS modem card plugged into the PCMCIA slot.

Anyway, thanks for the feedback. That's great, I know how to fix it.
_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send private message Visit poster's website 
Keef


Joined: 20 Dec 2007
Posts: 428
Location: Staffordshire
PostPosted: Wed 11 May 2011, 17:15    Post subject:  
Just to confirm that:

Code:
udevadm trigger --subsystem-match="pcmcia*"


worked for me too.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 7747
Location: Stratford, Ontario
PostPosted: Thu 12 May 2011, 10:27    Post subject:  
BarryK wrote:
# udevadm trigger --subsystem-match="pcmcia*"

This is interesting. There have been numerous reports of problems with recent Woof-built Puppies not detecting USB devices if they are already powered-on at boot-up.

I have seen this with certain printer-scanners where sane-find-scanner cannot detect the device, even though it is listed in lsusb and /sys/bus/usb.

A restart of the device makes it visible. This occurs in Wary 511, but not in older Puppies like Quirky 1.1.

However
Code:
 udevadm trigger --subsystem-match="usb*"

solves the problem without requiring a restart.
Back to top
View user's profile Send private message 
vickyg2003


Joined: 29 Apr 2011
Posts: 64
PostPosted: Thu 12 May 2011, 10:35    Post subject:  
I did a google search trying to understand what this command is doing, but that didn't help. What does this do?

I'm totally new to linux, and now that my puppy is working and doing exactly what I wanted to accomplish, I'd really like to become an informed user.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6856
Location: Perth, Western Australia
PostPosted: Thu 12 May 2011, 21:02    Post subject:  
rcrsn51 wrote:
BarryK wrote:
# udevadm trigger --subsystem-match="pcmcia*"

This is interesting. There have been numerous reports of problems with recent Woof-built Puppies not detecting USB devices if they are already powered-on at boot-up.

I have seen this with certain printer-scanners where sane-find-scanner cannot detect the device, even though it is listed in lsusb and /sys/bus/usb.

A restart of the device makes it visible. This occurs in Wary 511, but not in older Puppies like Quirky 1.1.

However
Code:
 udevadm trigger --subsystem-match="usb*"

solves the problem without requiring a restart.


rc.sysinit in Woof has --subsystem-match=usb, but I have now appended the *. The full line is now:

udevadm trigger --action=add --subsystem-match="pcmcia*" --subsystem-match="usb*" #110513
_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6856
Location: Perth, Western Australia
PostPosted: Thu 12 May 2011, 21:04    Post subject:  
vickyg2003 wrote:
I did a google search trying to understand what this command is doing, but that didn't help. What does this do?

I'm totally new to linux, and now that my puppy is working and doing exactly what I wanted to accomplish, I'd really like to become an informed user.


In google, type "man udevadm" to find the man page. It will take awhile to understand this stuff though.
_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 4944
Location: Australia
PostPosted: Fri 13 May 2011, 06:40    Post subject:  
It's great that the PCMCIA problem in Woof/Lupu appears close to being fixed ...
but I point out that there have been a few reports that simply getting the PCMCIA system initialised still did not provide a fix in certain cases.
peebee reported that an updated pcmciautils Lucid deb package was necessary -
http://www.murga-linux.com/puppy/viewtopic.php?p=446392#446392

and germanix went a step further by compiling various updated pcmciautils packages from scratch
http://www.murga-linux.com/puppy/viewtopic.php?p=488425#488425
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 4944
Location: Australia
PostPosted: Fri 13 May 2011, 06:41    Post subject:  
... and has anyone noticed that there have been quite a few reported instances of dhcpcd failures in Puppy 5.1/5.2?
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [14 Posts]  
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.0892s ][ Queries: 13 (0.0182s) ][ GZIP on ]