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 Mon 22 Dec 2014, 15:40
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Slacko 5.3.3 doesn't see PCMCIA card in Toshiba laptop
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 3 [32 Posts]   Goto page: Previous 1, 2, 3 Next
Author Message
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Tue 25 Sep 2012, 10:11    Post subject:  

rcrsn51 wrote:
You might have better luck trying an OLDER version, like Puppy 431.


I just finished trying it...and nothing.

I give up.

Thank you very much,

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

Joined: 10 Jun 2005
Posts: 5293
Location: Australia

PostPosted: Tue 25 Sep 2012, 20:14    Post subject:  

rcrsn51 wrote:
Type the command
Code:
lspci -nn

No no. "lspci" will only reveal the identity of the Cardbus controller device
- and in Elias' case, this device is "Toshiba ToPIC95".

To identify the Cardbus devices connected to the controller, you must follow the procedure I explained way back in 2006 -
http://www.murga-linux.com/puppy/viewtopic.php?p=31707#31707

Here it is again:
- Check if the PCMCIA system recognises your PCMCIA device with these 2 commands -
Code:
pccardctl status
pccardctl ident


If you cannot see your device listed, reset the Cardbus interface like this -
Code:
pccardctl eject
pccardctl insert


Now run "pccardctl ident" again.
If still no success, it's possible that Puppy failed to detect the Toshiba PCMCIA interface at boot up, and failed to initialise the PCMCIA subsystem (pcmciautils)
As a short term fix, run this command -
Code:
pcmcia-socket-startup

Now run "pccardctl ident" again - hopefully you will see a network device listed - then go ahead and run the Network Wizard to ensure the correct driver is loaded, and configure the network.

If this last step (running the "pcmcia-socket-startup" command) was successful, you can make this fix permanent by following forum member tubby's instructions to modify Puppy's start up script -
http://murga-linux.com/puppy/viewtopic.php?p=461413#461413
Back to top
View user's profile Send private message 
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Tue 25 Sep 2012, 23:11    Post subject:  

tempestuous wrote:
rcrsn51 wrote:
Type the command
Code:
lspci -nn

No no. "lspci" will only reveal the identity of the Cardbus controller device
- and in Elias' case, this device is "Toshiba ToPIC95".

To identify the Cardbus devices connected to the controller, you must follow the procedure I explained way back in 2006 -
http://www.murga-linux.com/puppy/viewtopic.php?p=31707#31707

Here it is again:
- Check if the PCMCIA system recognises your PCMCIA device with these 2 commands -
Code:
pccardctl status
pccardctl ident


If you cannot see your device listed, reset the Cardbus interface like this -
Code:
pccardctl eject
pccardctl insert


Now run "pccardctl ident" again.
If still no success, it's possible that Puppy failed to detect the Toshiba PCMCIA interface at boot up, and failed to initialise the PCMCIA subsystem (pcmciautils)
As a short term fix, run this command -
Code:
pcmcia-socket-startup

Now run "pccardctl ident" again - hopefully you will see a network device listed - then go ahead and run the Network Wizard to ensure the correct driver is loaded, and configure the network.

If this last step (running the "pcmcia-socket-startup" command) was successful, you can make this fix permanent by following forum member tubby's instructions to modify Puppy's start up script -
http://murga-linux.com/puppy/viewtopic.php?p=461413#461413


Hi tempestuous.

The device is listed - it's a Planet ENW-3502-2T - but the Network Wizard cannot see any active network interface even after running 'pcmcia-socket-startup'.

obs. I'm using slacko 5.3.3.

Elias
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 9376
Location: Stratford, Ontario

PostPosted: Tue 25 Sep 2012, 23:39    Post subject:  

I hunted around for more info about this device. I found several references to the ENW-3502-T where it was reported to work in Linux, but not the 2T.
Back to top
View user's profile Send private message 
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Tue 25 Sep 2012, 23:46    Post subject:  

rcrsn51 wrote:
I hunted around for more info about this device. I found several references to the ENW-3502-T where it was reported to work in Linux, but not the 2T.


Sorry, the card is in fact a ENW-3502-T, not a "2T".

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

Joined: 10 Jun 2005
Posts: 5293
Location: Australia

PostPosted: Wed 26 Sep 2012, 01:40    Post subject:  

Elias wrote:
The device is listed - it's a Planet ENW-3502-T

OK, that's a promising start.
When you run the "pccardctl ident" command, can you tell us exactly what information is reported for the card?
In particular, I want to know the device ID of the card - this is usually listed as "vendor ..." and "product ..."
Back to top
View user's profile Send private message 
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Wed 26 Sep 2012, 08:08    Post subject:  

tempestuous wrote:
Elias wrote:
The device is listed - it's a Planet ENW-3502-T

OK, that's a promising start.
When you run the "pccardctl ident" command, can you tell us exactly what information is reported for the card?
In particular, I want to know the device ID of the card - this is usually listed as "vendor ..." and "product ..."


Here is:

# pcardctl indent
Socket 0:
product info: "PLANET", "ENW-3502-T", "", ""
manfid: 0x8a01, 0x0100
function: 6 (network)
Socket 1:
no product info available

# pccardctl status
Socket 0:
5.0V 16-bit PC Card
Subdevice 0 (function 0) [unbound]
Socket 1:
no card
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5293
Location: Australia

PostPosted: Wed 26 Sep 2012, 09:49    Post subject:  

Elias wrote:
manfid: 0x8a01, 0x0100

Wow, that's an obscure device ID.
But Google indicates that the pcnet_cs driver should be compatible with your device, so I suggest you try to forcibly load this driver. There are various commands I can give you to load this driver, and also perform diagnostics to see how the driver loaded ... but for now, a quick and easy way is just to go to the Network Wizard, click on "Load module" then select "pcnet_cs" from the list.
Does the Wizard now report a valid network interface?
Back to top
View user's profile Send private message 
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Wed 26 Sep 2012, 11:58    Post subject:  

tempestuous wrote:
Elias wrote:
manfid: 0x8a01, 0x0100

Wow, that's an obscure device ID.
But Google indicates that the pcnet_cs driver should be compatible with your device, so I suggest you try to forcibly load this driver. There are various commands I can give you to load this driver, and also perform diagnostics to see how the driver loaded ... but for now, a quick and easy way is just to go to the Network Wizard, click on "Load module" then select "pcnet_cs" from the list.
Does the Wizard now report a valid network interface?


I already tried loading it. But after a few seconds the Wizard says that the interface was not found. In fact I tried all the modules with Wizard's autoprobe.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5293
Location: Australia

PostPosted: Thu 27 Sep 2012, 00:52    Post subject:  

Older Puppies used a PCMCIA/Cardbus subsystem called "pcmcia-cs" which relied on the hotplug mechanism and a configuration file - /etc/pcmcia/config - to match device ID's and descriptions to compatible PCMCIA drivers.
It's possible to modify that configuration file to change things.

But from Puppy 4.x onwards, our PCMCIA/Cardbus subsystem moved up to the "pcmciautils" system, which relies on udev.
I think that the matching of device ID's is done within the pccardctl utility, and this is difficult to modify.

So here's a long-shot - I have supplied you with an old-style configuration file which defines your device ID as being compatible with the pcnet_cs driver.
Go ahead and install this dotpet, then reboot.
Run the Network Wizard, and if you're lucky, the system may have autoamatically loaded the pcnet_cs driver and created an interface. If not, manually load the pcnet_cs driver as before.

If still no success, I'm reasonably confident that this configuration file would get you going with a version of Puppy Linux prior to ver 4.x.
I suggest Classic Pup 2.14X -
http://www.murga-linux.com/puppy/viewtopic.php?t=42553
PLANET-ENW-3502-T-config.pet
Description 
pet

 Download 
Filename  PLANET-ENW-3502-T-config.pet 
Filesize  878 Bytes 
Downloaded  190 Time(s) 
Back to top
View user's profile Send private message 
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Thu 27 Sep 2012, 07:07    Post subject:  

tempestuous wrote:
Older Puppies used a PCMCIA/Cardbus subsystem called "pcmcia-cs" which relied on the hotplug mechanism and a configuration file - /etc/pcmcia/config - to match device ID's and descriptions to compatible PCMCIA drivers.
It's possible to modify that configuration file to change things.

But from Puppy 4.x onwards, our PCMCIA/Cardbus subsystem moved up to the "pcmciautils" system, which relies on udev.
I think that the matching of device ID's is done within the pccardctl utility, and this is difficult to modify.

So here's a long-shot - I have supplied you with an old-style configuration file which defines your device ID as being compatible with the pcnet_cs driver.
Go ahead and install this dotpet, then reboot.
Run the Network Wizard, and if you're lucky, the system may have autoamatically loaded the pcnet_cs driver and created an interface. If not, manually load the pcnet_cs driver as before.

If still no success, I'm reasonably confident that this configuration file would get you going with a version of Puppy Linux prior to ver 4.x.
I suggest Classic Pup 2.14X -
http://www.murga-linux.com/puppy/viewtopic.php?t=42553


Tempestuous,

Unfortunately none of these options worked.

Thanks, Elias
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5293
Location: Australia

PostPosted: Thu 27 Sep 2012, 07:52    Post subject:  

I think that obscure device is too difficult to deal with in Linux.
It would cost you just a few dollars to replace it with an alternative Cardbus Lan card, or get a USB-LAN dongle instead ...
or forget about ethernet LAN, and get yourself a wifi card.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7841
Location: qld

PostPosted: Thu 27 Sep 2012, 08:35    Post subject:  

Hello Elias, tempestuous,

Just trying to do a binary chop here to rule out any pcmcia bugs.

My Marvel netgear wg511-v2 (wireless) is working fine here after disabling the onboard intel wireless. You may recall that one from a few years ago, tempestuous. Even working fine with WPA2-AES, albeit with ndiswrapper [ Rolling Eyes ].

This is running pfix=ram, from a usb stick on an IBM thinkpad r51, pentiumM (centrino) @1700MHz 400MHz FSB, 512 RAM shared, 32M for graphics, 533-4g version.

Elias, by your response, I gather you did try 2.14X?

Cheers

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
rcrsn51


Joined: 05 Sep 2006
Posts: 9376
Location: Stratford, Ontario

PostPosted: Thu 27 Sep 2012, 09:07    Post subject:  

FWIW, I found this post where someone got a Planet ENW-3502-T working in Debian using the old-style PCMCIA system.
Back to top
View user's profile Send private message 
Elias

Joined: 23 Sep 2012
Posts: 18

PostPosted: Thu 27 Sep 2012, 10:13    Post subject:  

01micko wrote:


Elias, by your response, I gather you did try 2.14X?

Cheers


Yes, I tried tempestouos' pet in 5.3.3 and 2.14X.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 3 [32 Posts]   Goto page: Previous 1, 2, 3 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.1003s ][ Queries: 13 (0.0052s) ][ GZIP on ]