[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
Dunbrokin, yours seems to be another bug. Because: 1. you - at least sometimes - see your interface through ifconfig. 2. your card uses another driver than mine 3. the driver reports problems due to 32bit I/O, are you running a 64 bit version? - if yes the problem could be the driver not beeing compatible with 64 bit kernel. Actually, the I/O timing problems the driver predicts do happen, thus this could be the issue Therefore, maybe it is better if you report another bug. Remember to _attach_ in your bug report the files generated by the following comands: uname -a > uname-a.log cat /proc/version_signature > proc_version_signature.log sudo lspci -vvnn > lspci-vvnn.log (those are 2 v's not a w) dmesg > dmesg.log sudo lspcmcia -vv > lspcmcia-vv.log That means, that you have to attach five different files. Additionally, you say, that the card worked under kde 4.1 - unfortunately, hardware-issues are usually independent from the window manager / desktop suite and therefore you should maybe add the information, wich distro/version you were running (hardy?), the best would be to attach the output of dmesg -a > dmesg-a.log.workedBefore It would be really kind if you could take the time to gather these information and add it do a new bug report. Hopefully some developers can then fix the bug, so that you and everybody else with a similar hardware configuration can enjoy intrepid final. Thanks, Mika -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
I have a similar problem with my PCMCIA cardit worked perfectly under 8.04 but now cannot see the router. Here is a printout: [EMAIL PROTECTED]:~$ sudo lshw -C Network *-network description: Ethernet interface product: 3c556B CardBus [Tornado] vendor: 3Com Corporation physical id: 3 bus info: [EMAIL PROTECTED]:00:03.0 logical name: eth0 version: 20 serial: 00:04:76:60:6f:87 size: 10MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=3c59x duplex=half latency=64 link=no maxlatency=10 mingnt=10 module=3c59x multicast=yes port=MII speed=10MB/s *-network DISABLED description: Wireless interface product: ACX 111 54Mbps Wireless Interface vendor: Texas Instruments physical id: 1 bus info: [EMAIL PROTECTED]:06:00.0 logical name: wlan0 version: 00 serial: 00:0f:3d:57:76:56 width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=acx_pci latency=64 module=acx multicast=yes wireless=IEEE 802.11b+/g+ *-network DISABLED description: Ethernet interface physical id: 1 logical name: pan0 serial: d2:f8:de:93:ae:85 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes [EMAIL PROTECTED]:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 03) 00:02.0 CardBus bridge [0607]: Texas Instruments PCI1450 [104c:ac1b] (rev 03) 00:02.1 CardBus bridge [0607]: Texas Instruments PCI1450 [104c:ac1b] (rev 03) 00:03.0 Ethernet controller [0200]: 3Com Corporation 3c556B CardBus [Tornado] [10b7:6056] (rev 20) 00:03.1 Communication controller [0780]: 3Com Corporation Mini PCI 56k Winmodem [10b7:1007] (rev 20) 00:05.0 Multimedia audio controller [0401]: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] [1013:6003] (rev 01) 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02) 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) 00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01) 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) 01:00.0 VGA compatible controller [0300]: S3 Inc. 86C270-294 Savage/IX-MV [5333:8c12] (rev 13) 06:00.0 Network controller [0280]: Texas Instruments ACX 111 54Mbps Wireless Interface [104c:9066] [EMAIL PROTECTED]:~$ dmseg | grep -e iwl -e wlan -e rt -e ath bash: dmseg: command not found [EMAIL PROTECTED]:~$ dmesg | grep -e iwl -e wlan -e rt -e ath [ 0.00] Movable zone start PFN for each node [ 0.00] ACPI: PM-Timer IO Port: 0x1008 [ 0.00] Allocating PCI resources starting at 3000 (gap: 2000:dff8) [ 0.00] Enabling unmasked SIMD FPU exception support... done. [ 0.004000] virtual kernel memory layout: [ 0.881353] Booting paravirtualized kernel on bare hardware [ 1.365536] ACPI: (supports S0 S1 S3 S4 S5) [ 1.626629] ACPI: EC: driver started in interrupt mode [ 1.628743] pci :00:02.0: supports D1 [ 1.628753] pci :00:02.0: supports D2 [ 1.628764] pci :00:02.0: PME# supported from D0 D1 D2 D3hot D3cold [ 1.628864] pci :00:02.1: supports D1 [ 1.628873] pci :00:02.1: supports D2 [ 1.628883] pci :00:02.1: PME# supported from D0 D1 D2 D3hot D3cold [ 1.628959] PCI: :00:03.0 reg 10 io port: [1800, 18ff] [ 1.629065] pci :00:03.0: supports D1 [ 1.629074] pci :00:03.0: supports D2 [ 1.629085] pci :00:03.0: PME# supported from D0 D1 D2 D3hot D3cold [ 1.629149] PCI: :00:03.1 reg 10 io port: [2000, 20ff] [ 1.629243] pci :00:03.1: supports D2 [ 1.629254] pci :00:03.1: PME# supported from D0 D2 D3hot D3cold [ 1.629413] pci :00:05.0: supports D1 [ 1.629422] pci :00:05.0: supports D2 [ 1.629561] PCI: :00:07.1 reg 20 io port: [1c00, 1c0f] [ 1.629659] PCI: :00:07.2 reg 20 io port: [1c20, 1c3f] [ 1.630050] pci :01:00.0: supports D1 [ 1.630060] pci :01:00.0: supports D2 [ 1.672879] Linux Plug and Play Support v0.97 (c) Adam Belay [ 1.804694] system 00:02: ioport range 0x1000-0x103f has been reserved [ 1.804709] system 00:02: ioport range 0x1040-0x104f has been reserved [ 1.804725] system 00:02: ioport range 0xfe00-0xfe0f has been reserved [ 1.804778] system 00:09: ioport range 0x15e0-0x15ef has been reserved [ 1.848667] bus: 00 index 0 io port: [0, ] [ 1.848730] bus: 02 index 0 io port: [1400, 14ff] [ 1.848741] bus: 02 index 1 io port: [2400, 24ff] [ 1.848774] bus: 06 index 0 io port: [2800, 28ff] [ 1.848784] bus: 06 index 1 io port: [2c00, 2cff] [ 4.290293] Serial: 8250/16550 driver4 ports, IRQ sharing enabled [ 4.320603] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 4.320626] serio:
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
Yes, it is loaded automatically on boot time and it is used by the modules pcmcia_core and pcmcia (as lsmod shows). I really don't know much about the linux driver system, but to me it looks as if pcnet_cs fails to be somehow bound to the pcmcia card. In dmesg you can see, that pcnet_cs (or somebody else with the name 'cs') even probes IO ports on boot time. So it is loaded in the kernel. Thanks for your efforts so far, Chris. -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
spiderbatdad - yours is a different problem. Please open a new bug report. Mika - Are you saying that the pcnet_cs module is already loaded automatically when you boot? Thanks -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
I am having the same problem on my friends machine...the card worked wel in gutsy and hardy. The following occurs during boot now...intrepid 2.6.27-5 [ 271.664079] wlan0: issue_cmd(): timed out waiting for CMD_COMPLETE. irq bits:0x irq_status:0x timeout:49ms cmd_status:0 (Idle) [ 271.664104] wlan0: issue_cmd(cmd:0x0002) FAILED [ 271.664118] Pid: 4903, comm: NetworkManager Not tainted 2.6.27-5-generic #1 [ 271.664130] [] ? printk+0x1d/0x1f [ 271.664177] [] acxpci_s_issue_cmd_timeo+0x269/0x3b0 [acx] [ 271.664268] [] acx_s_configure+0x99/0xc0 [acx] [ 271.664293] [] acx_s_update_card_settings+0x5f7/0x1110 [acx] [ 271.664318] [] ? hrtick_start_fair+0x181/0x1a0 [ 271.664350] [] acx_ioctl_commit+0x26/0x40 [acx] [ 271.664370] [] ? acx_ioctl_commit+0x0/0x40 [acx] [ 271.664391] [] ioctl_standard_call+0xbc/0x110 [ 271.664409] [] ? __dev_get_by_name+0x85/0xb0 [ 271.664425] [] wireless_process_ioctl+0xbe/0x150 [ 271.664438] [] ? acx_ioctl_set_encode+0x0/0x1a0 [acx] [ 271.664459] [] ? mutex_lock+0x10/0x20 [ 271.664470] [] wext_handle_ioctl+0x70/0xe0 [ 271.664482] [] ? ioctl_standard_call+0x0/0x110 [ 271.664494] [] ? ioctl_private_call+0x0/0x180 [ 271.664507] [] dev_ioctl+0x45f/0x520 [ 271.664518] [] ? inet_create+0x229/0x300 [ 271.664531] [] ? _spin_lock+0xd/0x10 [ 271.664543] [] ? inotify_d_instantiate+0x45/0x60 [ 271.664559] [] ? security_d_instantiate+0x18/0x30 [ 271.664578] [] ? d_instantiate+0x57/0x60 [ 271.664592] [] ? sock_ioctl+0x0/0x250 [ 271.664605] [] sock_ioctl+0xf5/0x250 [ 271.664614] [] ? sock_ioctl+0x0/0x250 [ 271.664624] [] vfs_ioctl+0x2d/0x90 [ 271.664638] [] do_vfs_ioctl+0x66/0x1f0 [ 271.664650] [] sys_ioctl+0x6b/0x70 [ 271.664661] [] sysenter_do_call+0x12/0x2f [ 271.664677] === [ 271.664684] wlan0: configure(type:0x1010) FAILED [ 271.724128] wlan0: issue_cmd(): timed out waiting for CMD_COMPLETE. irq bits:0x irq_status:0x timeout:49ms cmd_status:0 (Idle) [ 271.724160] wlan0: issue_cmd(cmd:0x0016) FAILED [ 271.724173] Pid: 4903, comm: NetworkManager Not tainted 2.6.27-5-generic #1 [ 271.724185] [] ? printk+0x1d/0x1f [ 271.724230] [] acxpci_s_issue_cmd_timeo+0x269/0x3b0 [acx] [ 271.724322] [] acx_s_set_probe_request_template+0x14a/0x160 [acx] [ 271.724354] [] acx_s_update_card_settings+0xca3/0x1110 [acx] [ 271.724378] [] ? enqueue_hrtimer+0x7d/0x120 [ 271.724398] [] ? hrtimer_start+0xc4/0x1c0 [ 271.724413] [] ? hrtick_start_fair+0x181/0x1a0 [ 271.724431] [] ? check_preempt_wakeup+0x14d/0x1b0 [ 271.72] [] ? try_to_wake_up+0xde/0x290 [ 271.724457] [] ? __nla_put+0x1d/0x50 [ 271.724477] [] ? wireless_send_event+0x15f/0x230 [ 271.724497] [] acx_ioctl_commit+0x26/0x40 [acx] [ 271.724517] [] ? acx_ioctl_commit+0x0/0x40 [acx] [ 271.724538] [] ioctl_standard_call+0xbc/0x110 [ 271.724551] [] wireless_process_ioctl+0xbe/0x150 [ 271.724563] [] ? acx_ioctl_set_mode+0x0/0xc0 [acx] [ 271.724583] [] ? mutex_lock+0x10/0x20 [ 271.724595] [] wext_handle_ioctl+0x70/0xe0 [ 271.724606] [] ? ioctl_standard_call+0x0/0x110 [ 271.724618] [] ? ioctl_private_call+0x0/0x180 [ 271.724631] [] dev_ioctl+0x45f/0x520 [ 271.724646] [] ? inet_create+0x229/0x300 [ 271.724659] [] ? _spin_lock+0xd/0x10 [ 271.724671] [] ? inotify_d_instantiate+0x45/0x60 [ 271.724690] [] ? security_d_instantiate+0x18/0x30 [ 271.724708] [] ? d_instantiate+0x57/0x60 [ 271.724722] [] ? sock_ioctl+0x0/0x250 [ 271.724736] [] sock_ioctl+0xf5/0x250 [ 271.724746] [] ? sock_ioctl+0x0/0x250 [ 271.724756] [] vfs_ioctl+0x2d/0x90 [ 271.724770] [] do_vfs_ioctl+0x66/0x1f0 [ 271.724782] [] sys_ioctl+0x6b/0x70 [ 271.724792] [] sysenter_do_call+0x12/0x2f [ 271.724810] === [ 271.784104] wlan0: issue_cmd(): timed out waiting for CMD_COMPLETE. irq bits:0x irq_status:0x timeout:49ms cmd_status:0 (Idle) [ 271.784120] wlan0: issue_cmd(cmd:0x000B) FAILED [ 271.784134] Pid: 4903, comm: NetworkManager Not tainted 2.6.27-5-generic #1 [ 271.784147] [] ? printk+0x1d/0x1f [ 271.784188] [] acxpci_s_issue_cmd_timeo+0x269/0x3b0 [acx] [ 271.784278] [] acx_s_cmd_join_bssid+0x1b2/0x1f0 [acx] [ 271.784307] [] acx_s_update_card_settings+0x30c/0x1110 [acx] [ 271.784330] [] ? enqueue_hrtimer+0x7d/0x120 [ 271.784350] [] ? hrtimer_start+0xc4/0x1c0 [ 271.784365] [] ? hrtick_start_fair+0x181/0x1a0 [ 271.784383] [] ? check_preempt_wakeup+0x14d/0x1b0 [ 271.784397] [] ? try_to_wake_up+0xde/0x290 [ 271.784410] [] ? __nla_put+0x1d/0x50 [ 271.784430] [] ? wireless_send_event+0x15f/0x230 [ 271.784451] [] acx_ioctl_commit+0x26/0x40 [acx] [ 271.784472] [] ? acx_ioctl_commit+0x0/0x40 [acx] [ 271.784493] [] ioctl_standard_call+0xbc/0x110 [ 271.784506] [] wireless_process_ioctl+0xbe/0x150 [ 271.784519] [] ? acx_ioctl_set_mode+0x0/0xc0 [acx] [ 271.784539] [] ? mutex_lock+0x10/0x20 [ 271.784550] [] wext_handle_ioctl+0x70/0xe0 [ 271.784562] [] ? ioctl_standard_call+0x0/0x110 [
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
Hi, shortly: it doesn't happen anything. long version: I describe what I do, just in case I misunderstood you. I boot intrepid, log in and run sudo modprobe pcnet_cs No output at all, dmseg|tail does not reveal any messages since boottime. No other log in /var/log that I checked has any messages. Thus I reboot and try this time sudo modprobe -v --first-time pcnet_cs to get at least some output. I get FATAL: Module pcnet_cs already in kernel. To check that, I reboot and say lsmod | grep pcnet_cs (output see attachment, four lines) and then I sudo modprobe. After loading the driver manually lsmod looks the same (lsmod|grep pcnet_cs gives the same four lines, I diffed them, it is exactly the same, as in the attachment) In ifconfig the network interface does not show up. I don't know if there is a way to manually bind a driver to a pcmcia- card (at least pccardctl does not have this function), if there is a way, I'd give it a try. ** Attachment added: "lsmod_grep_pcnet_cs.log" http://launchpadlibrarian.net/18234445/lsmod_grep_pcnet_cs.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
Mika, what happens if you manually load the pcnet_cs driver: sudo modprobe pcnet_cs -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
It just came to my mind that this might matter as well (I almost forgot it because it is so everyday for me...): I am booting the kernel with the kerneloption pci=irqmask=0x0e98. That is because neither pci=biosirq nor without any pci-options wrok. Both fail to detect the harddrive and the cd-rom drive, although they are both standard IDE (or at least claim to be). I read about the pci=irqmask=0x0e98 option that it is required for this notebook, and actually you won't get far without (it won't boot), this is known for this laptop at least since 2001. I don't use other kernel boot parameters, only ro, pci=irqmask=0x0e98 and nosplash. ** Attachment removed: "outputs" http://launchpadlibrarian.net/18225359/outputs -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "HARDY_WORKS_uname-a.log" http://launchpadlibrarian.net/18231874/HARDY_WORKS_uname-a.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "HARDY_WORKS_proc_version_signature.log" http://launchpadlibrarian.net/18231850/HARDY_WORKS_proc_version_signature.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "HARDY_WORKS_lspcmcia-vv.log" http://launchpadlibrarian.net/18231845/HARDY_WORKS_lspcmcia-vv.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "HARDY_WORKS_lspci-vvnn.log" http://launchpadlibrarian.net/18231837/HARDY_WORKS_lspci-vvnn.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "HARDY_WORKS_dmesg.log" http://launchpadlibrarian.net/18231555/HARDY_WORKS_dmesg.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "uname-a.log" http://launchpadlibrarian.net/18231542/uname-a.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "proc_version_signature.log" http://launchpadlibrarian.net/18231535/proc_version_signature.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "lspcmcia-vv.log" http://launchpadlibrarian.net/18231528/lspcmcia-vv.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/18231518/lspci-vvnn.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/18231503/dmesg.log -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments. ** This bug is no longer a duplicate of bug 256054 [intrepid] new 0.7 branch ignores /etc/network/interfaces ** Changed in: linux (Ubuntu) Importance: Undecided => Medium Status: New => Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Chris Coulson (chrisccoulson) ** Tags added: regression-potential -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
*** This bug is a duplicate of bug 256054 *** https://bugs.launchpad.net/bugs/256054 Hi, I don't think the bug is a duplicate of bug #256054, because: 1. I tried the workaround described at bug #256054, that means I disabled the NetworkManager completely. It isn't loaded anymore (does not appear in boot log, or whatever the name of the output ist, that you get when you give nosplash at boot prompt) and 'ps aux | grep net' does not show any running instances (of course after a reboot after disabling the NetworkManager). Although NetworkManager can't do anything anymore, the dmesg-output is the same (not exactly, NetworkManager does not appear in dmesg, but it didn't appear around the PCMCIA-probes before, anyway, as I point out later), eth0 does not appear in ifconfig-output, and lspcmcia-vv gives exactly the same output. Or in short: It didn't change anything. 2. The problem arises far earlier than NetworkManager is being loaded. The problem arises during the stage in booting process when the hardware drivers are being loaded. That is before any runlevel. After that, when entering runlevel 2, roughly, ifup is excuted (without any special impact, as /dev/eth0 does not exist) and way after that (when entering runlevel 5), NetworkManager is executed and /could/ indeed interfere with any settings, if there would even be a network device. But there is none, and there are no special settings, it would just work fine with DHCP, if NM would set any device to that, but there is no networking device (virtually, physically it is sitting there blinking). Furthermore, before removing NetworkManager I could access NetworkManager and it was reporting "No ethernet device" or something like this. That means I can confirm that NetworkManager did not find any devices and can therefore not mess the configuration of these. So I would say this is not a duplicate of bug #256054. -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
*** This bug is a duplicate of bug 256054 *** https://bugs.launchpad.net/bugs/256054 I looked quickly what the driver axnet_cs (that is proposed by pnet_cs) is for: it is for spcial AXIS-based cards. I did not find any hints that the Netgear FA411 card is based on this chipset. I would rather say, it ist not. So maybe the error is, that pcnet_cs falsely detects an AXIS card. -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
*** This bug is a duplicate of bug 256054 *** https://bugs.launchpad.net/bugs/256054 ** This bug has been marked a duplicate of bug 256054 [intrepid] new 0.7 branch ignores /etc/network/interfaces -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278350] Re: [intrepid-beta] PCMCIA network-card working in hardy does not work
** Attachment added: "outputs" http://launchpadlibrarian.net/18225359/outputs -- [intrepid-beta] PCMCIA network-card working in hardy does not work https://bugs.launchpad.net/bugs/278350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
