The fix worked for my system. Thanks!
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
linux-source-2.6.22 (2.6.22-14.41) gutsy; urgency=low
[Ben Collins]
* ubuntu/d-i: Add niu to nic-modules
[Kyle McMartin]
* vesafb is not for ia64
* remove CONFIG_NIU from places it shouldn't be
* fix orinoco_cs oops
- LP: #149997
[Upstream Kernel Changes]
* [SPARC64]: Allo
Assigning to the kernel team per their bug policy.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug noti
** Changed in: linux-source-2.6.22 (Ubuntu)
Target: None => ubuntu-7.10-rc
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
fwiw my patch is at people.ubuntu.com/~kyle/orinoco_cs_fix.diff
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Hi, your patch looks (mostly) correct, and is similar to what I've put
into gutsy. Thanks!
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
A valid point. I think a fix that involves only one call to
pcmcia_register_driver is the best option. I think the original
bug/panic was caused by attempting to register twice when the first call
succeeded. My != prevents the second call, but does disable the second
set of devices. Is it possi
I'm using the orinoco_cs driver with this patch (applies against
2.6.22-13.40) to send this attachment, so it seems to work.
FWIW, if the first pcmcia_register_driver call succeeds but the second
one fails ,then removing the module will probably cause a kernel panic.
I think I'll try to make anoth
"For those devices, the first call to pcmcia_register_driver will fail"
No, the first call is still going to succeed. Remember, you can load a
module (and therefore register the driver) for a device which is not yet
present!
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https:
My understanding is that the orinoco_driver set of PCMCIA IDs is
exported to allow auto-detection of those devices as belonging to
orinoco_cs. IOW, if a device with an ID in orinoco_driver is
hotplugged, orinoco_cs will automatically be loaded to support this
device. Devices in orinoco_overlap_dr
David's suggestion happens to work, but I think it leaves the driver
broken in a more subtle manner (ISTM that a pcmcia_register_driver error
could change the set of supported devices for no rational reason -- and
even if that's not the case, IMO there are other reasons why the code
doesn't quite m
Linux 2.6.22.9 does not have this bug. Linux 2.6.22.9 with
2.6.22-13.40's orinoco_cs.c does have this bug. So, I'm pretty sure that
the bug is in orinoco_cs.c.
At this point, I don't think the fix is as simple as what David
suggests, but I'm still in the process of trying to understand the
situati
Here's the syslog I get when I insert a orinoco_cs-supported card.
** Attachment added: "syslog with kernel backtrace"
http://launchpadlibrarian.net/9858046/orinoco_backtrace.txt
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You receiv
orinoco_cs causes kernel backtraces the first time I insert the card and
hangs the kernel on the second insert.
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bugs, which
Meanwhile I solved the problem temporarily this way: I booted from grub
using the older kernel and from there removed the new kernel using the
adept. So far it worked. Let's see if I'll get the next update.
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.ne
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
A couple of seconds before the kernel actually starts booting, you
should be able to press Esc. Then you should get a menu that lets you
choose kernels.
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification becau
My problem is that the card is not removable, at least not without
opening the whole notebook. So how can I fix the problem, since I can't
boot and therefore can't get an update?
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received t
My steps for reproducing the bug also work if you install Gutsy beta
instead of Tribe 5 in step 1 -- I just tested this.
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received this bug notification because you are a member of Ubuntu
Bu
I have a SUSPICION (untested) as to the source of this bug. In commit
0fd77efbd8364d6a2625bbc4b84c1f3c26387655, the following code appears:
static int __init
init_orinoco_cs(void)
{
+ int status;
+
printk(KERN_DEBUG "%s\n", version);
- return pcmcia_register_driver(&orinoco_driver);
+ status = p
No; it happens as soon as the card is inserted. Without the card
inserted (Orinoco PCMCIA card), boot sequence completes. As soon as the
card is inserted, there is a hard lockup. No keyboard, no mouse, etc
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.
Just to clarify something - for those of you using external cards, this
only happens if the card is inserted at boot, right?
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => Critical
Status: New => Confirmed
--
2.6.22-13 freezes during boot (related somehow to orino
Well, at least, this includes as much of the panic as I could get. I
started up with "vga=ask" and chose the 80x60 option, but something
during the boot process undoes that (at least partially) before the
panic happens...
** Attachment added: "screenshot of the kernel panic"
http://launchpadlib
A system going from feisty -> gutsy tribe 4 -> continuous updates to
current exhibits the same behavior. The call trace is the same on mine
as well. This is a fairly major bug.
--
2.6.22-13 freezes during boot (related somehow to orinoco_cs)
https://bugs.launchpad.net/bugs/149997
You received t
Oh, by the way, here's how I'm reproducing this bug, starting from
scratch:
1. Plug the computer into a wired network connection.
2. Install Gutsy Tribe 5.
3. Reboot into the newly installed system.
4. Run Update Manager.
5. Click "Check."
6. Perform a "partial upgrade" when prompted.
7. Once the
Same bug with my laptop. I don't know what it means, but I have a
Orinoco Wireless LAN PC card (3.3 Volt) connected to a Texas Instruments
PCI-1410 Cardbus Controller (PCMCIA-Adapter). Anyhow, my Laptop can't
boot since the last Update today.
--
2.6.22-13 freezes during boot (related somehow to o
26 matches
Mail list logo
