| View previous topic :: View next topic |
| Author |
Message |
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
 Posted: Tue Jan 11, 2005 2:08 am Post subject: Wireless (prism54) problem after kernel upgrade |
 |
|
Hello All
Booted into new kernel today (gentoo-dev-sources-2.6.10-r4). All of sudden my wireless interface is not found?!?
When I start my interface, I get the following error:
| Code: | # /etc/init.d/net.eth1 start
* Running preup function
* eth1 does not exist
* preup eth1 failed |
I thought it was a problem with the prism54 module.. I tried to re-emerge prism54.. which bombed, but I was reminded that 2.6 kernels have support and that it was already loaded.
Booting back into the old kernel (gentoo-dev-sources-2.6.9-gentoo-r13) gave me wireless capabilities.
Trying to further debug the problem, I booted back into the 2.6.10 kernel and verify that prism54 is being loaded...
from dmesg:
| Code: | | Loaded prism54 driver, version 1.2 |
from /var/log/messages:
| Code: | Jan 10 18:55:23 hanji rc-scripts: eth1 does not exist
Jan 10 18:55:23 hanji rc-scripts: preup eth1 failed |
from lsmod:
| Code: | prism54 53000 0
firmware_class 7552 1 prism54 |
from ifconfig:
| Code: | # ifconfig eth1 up
eth1: unknown interface: No such device |
Any help is greatly appreciated, I feel pretty stuck.
Thanks!
hanji |
|
| Back to top |
|
 |
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Tue Jan 11, 2005 10:04 am Post subject: |
|
|
| I had a similar issue - turned out that my pcmcia config had not been brought across correctly when copying .config files |
|
| Back to top |
|
|
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
| Posted: Tue Jan 11, 2005 4:57 pm Post subject: |
|
|
Hello UberLord
Thanks for replying.. hoping you would!
Well.. diff'ing my configs.. I see what you are talking about. The 2.6.10 config didn't have:
| Code: | CONFIG_PCMCIA=y
CONFIG_PCMCIA_DEBUG=y
CONFIG_YENTA=y
CONFIG_CARDBUS=y
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y
|
I'm recompiling now.. will post if I have sucess || failure.
Thanks!
hanji |
|
| Back to top |
|
|
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
| Posted: Tue Jan 11, 2005 5:11 pm Post subject: |
|
|
Ok.. kernel rebuild/reboot did jack.
I looked at the .config after recompile/reboot.. and all my options are gone again. Is this a bug with 2.6.10 kernel? I manually changed them again, but after recompile.. the .config returns back to the options not available?
Any ideas?
thanks
hanji |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Tue Jan 11, 2005 6:01 pm Post subject: |
|
|
| They saved for me - is your .config file writeable? |
|
| Back to top |
|
|
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
| Posted: Tue Jan 11, 2005 6:09 pm Post subject: |
|
|
Hello
Yes.. .config file is writable. When you add those options, do you see them when you do make menuconfig? In my case I do not see the those options at all. I've tried this by editing/saving the .config file directly and rebuilding the kernel, and by applying make menuconfig. make menuconfig always leads to those options to be commented out.. and after re-compile, those options are completely gone. It seems like make is overwriting my .config file? All other settings for my box remain the same and are functional.. only pcmcia stuff is getting horked.
Are you using gentoo-dev-sources as well?
Thanks!
hanji |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Wed Jan 12, 2005 2:00 am Post subject: |
|
|
Yes I see them - although menuconfig pcmcia bit looks to have changed a bit (can't be sure though)
And yes, I use gentoo-dev-sources |
|
| Back to top |
|
|
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
|
| Back to top |
|
|
warpster
n00b
Joined: 26 Dec 2004
Posts: 31
|
| Posted: Wed Jan 12, 2005 5:20 am Post subject: bump |
|
|
OK, so I finally decided to ask for help with this, after trying to get it to work for hours... and there's already a topic covering almost the same exact problem! Once again, feels good to know you're not the only one. 
Anyway, I'm having problems with 2.6.10-gentoo-r4 and a Prism card as well.
Here's what seems to be the only Prism-related line returned by the kernel at boot: | Quote: | PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
ACPI: PCI interrupt 0000:06:00.0[A]: no GSI - using IRQ 0
eth0: could not install IRQ handler
prism54: probe of 0000:06:00.0 failed with error -5 |
A-ha! IRQ related... Reading more in dmesg I learned that PCI IRQs are no longer routed automatically. And according to lspci, the Prism card is 0000:06:00.0, so it would look like we're hitting the mark here. Conceivably, the driver could be failing to call pci_enable_device, so I tried the pci=routeirq kernel parameter to temporarily revert to the old behavior. No joy.
Stubbornly, I attempted to bring eth1 up anyway ("It's SUPPOSED to work!"), but this (not surprisingly) was the result: | Quote: | * Bringing eth1 up (192.168.0.10)...
SIOCSIFADDR: No such device
eth1: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth1: unknown interface: No such device
SIOCSIFNETMASK: No such device |
Which reminds me: The really weird thing about the dmesg error above is that the Prism card is supposed to be eth1, not eth0. I have no idea why it probes eth0 (failing), and whether this means that it stops there instead of attempting to probe the other socket. cardmgr sees both sockets, and lspci sees the card just fine, with manufacturer info and all. I have no idea how to tell prism54 that the card it's looking for is on the other socket, if that's what I should do.
Eventually, I tried following UberLord's HOWTO (URL: https://forums.gentoo.org/viewtopic.php?t=122435), which entailed emerging a ~x86 baselayout, which brought with it a new bash, sysvinit, etc. These bleeding edge packages seemed to make my console unstable and somewhat unreliable (weird errors, lines pasting out of nowhere, so on and so forth), and the included scripts didn't seem to work either. Same prism54 error msg, too, so I figured the problem must be much earlier, and reverted to my stable baselayout and the old method (which at least works with my *wired* card!).
At this point I have absolutely no clue what to do. Can anyone help? Here's some links to some useful info about my system. I'm linking to them only because several of them are pretty large chunks of text. If you need more information just let me know:
1) lspci output (URL: http://www.corridorofmadness.com/gentoo/lspci.output);
2) dmesg output, the whole thing (URL: http://www.corridorofmadness.com/gentoo/dmesg.output);
3) kernel configuration (/usr/src/linux/.config), the whole thing (URL: http://www.corridorofmadness.com/gentoo/usr/src/linux/.config);
4) contents of /etc/conf.d/net (URL: http://www.corridorofmadness.com/gentoo/etc/conf.d/net).
It's also worth noting that some of the options that you guys were talking about above don't seem to be available through menuconfig. What's up with that? Normally, I'd take such a thing to mean that those options are deprecated and replaced with something better and/or more built-in, but I get the feeling that might be a little over-optimistic in this case.
Anyway, enough already. Any and all help will be most appreciated. Thank you so much in advance!
warpster |
|
| Back to top |
|
|
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
| Posted: Wed Jan 12, 2005 5:29 am Post subject: |
|
|
It's nice to see someone have similar problems! I'm also noticing another bit of odd behaviour with 2.6.10 kernel.. firefox seems to behave sluggishly, painting the screen slower than normal... as if CPU was pegged. Dropping down to 2.6.9, and firefox is snappy as ever again. This may be related to the reiser patch mentioned in the link I posted. I have not patched my kernel yet with the reiser patch.. but thought I should mention this.
Hopefully we'll get something figured out soon.
hanji |
|
| Back to top |
|
|
warpster
n00b
Joined: 26 Dec 2004
Posts: 31
|
| Posted: Wed Jan 12, 2005 10:03 am Post subject: |
|
|
| just a lil' bump before giving up |
|
| Back to top |
|
|
hanj
Veteran
Joined: 19 Aug 2003
Posts: 1500
|
| Posted: Wed Jan 12, 2005 9:41 pm Post subject: |
|
|
I was able to get my interface up. The problem is that your config needs to be tweaked exactly to match your 2.6.9 kernel. I had PCCard support built as module.. I built this in.. still had problems. I also did not have 32-bit CardBus Support built in.. which in turn didn't give me yenta. I was trying to push these config options manually by editing the config directly, instead of looking closely at the areas they reside and building that support in.
I also noticed.. I now have to have pcmcia in default runlevel to start.. as before I did not.. when I had net.eth0 in default (wired interface) it would handle the preup for me on boot.
My Firefox performance is still horrible.. not sure what this could be still.. and it's driving me crazy
Here is my menuconfig section .. it may help
| Code: | <*> PCCard (PCMCIA/CardBus) support
[*] Enable PCCARD debugging
[ ] Enable obsolete PCCARD code
<M> 16-bit PCMCIA support
[*] 32-bit CardBus support
--- PC-card bridges
<M> CardBus yenta-compatible bridge support
< > Cirrus PD6729 compatible bridge support
<M> i82092 compatible bridge support
<M> i82365 compatible bridge support |
hanji |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Thu Jan 13, 2005 9:31 am Post subject: |
|
|
You don't need the pcmcia-cs package unless you're using 16-bit pcmcia cards really as hotplug takes care of 32-bit cards.
You do loose the cardinfo program, but lspci reports the card anyway, so it's not that much of a big deal. |
|
| Back to top |
|
|
|
Networking & Security
