From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)
Date: Sat, 25 Nov 2006 20:48:00 +0000 [thread overview]
Message-ID: <200611252048.16847.michaelkintzios@gmail.com> (raw)
In-Reply-To: <5bdc1c8b0611251229l61dc420es30f92c0bebafe316@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
On Saturday 25 November 2006 20:29, Mark Knecht wrote:
> Hi,
> I've been upgrading a couple of machines. Things are going fairly
> well but there have been a few problems. This one I need to work out
> first.
>
> 1) My son's machine was rebuilt with gcc-4 following the upgrade
> guide. Everything went well and it finished up yesterday afternoon.
> Since I use ndiswrapper on that machine I rebuilt the kernel with
> gcc-4 and I rebooted with the new kernel and new drivers. Everything
> worked great including wireless, MythTV frontend, Aqualung, etc.
>
> 2) This morning I cold booted and everything worked. I did an eix-sync
> and had a couple of things to build so I did that. One of them was new
> a udev package. Coldplug was removed from the machine.
>
> 3) I *think* I warm booted at this point and things still worked but
> I'm not positive on that. However I then booted the machine into
> Windows to check that it was still there for games, and then warm
> booted back into Gentoo. At this point wireless was completely gone. I
> tried cold booting but that didn't help so I don't think running
> Windows made any real difference.
>
> a) /etc/init.d/net.wlan0 stays it's stopped. If I try to start wlan0
> I'm told it doesn't exist.
>
> b) I have the link from net.wlan0 to net.lo.
>
> c) I rebuilt ndiswrapper and it loads. ndiswrapper -l tells me that
> the driver is loaded and the device is present.
>
> d) All the basic stuff like route doesn't see the interface, as
> expected I guess.
>
> Where might I look for what's gone wrong?
>
> As an aside, the Gentoo kernels remove support for stack size
> changes so ndiswrapper complains about the kernel when it's emerged.
> Is there a patch to get an 8K stack size option back again? Why does
> anyone remove this in the first place instead of just setting it to a
> sane default?
>
> Sorry I Cannot send any info from the box but it's off the net.
In case you haven't, remerge/modprobe the module for the wifi card.
HTH.
--
Regards,
Mick
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-25 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 20:29 [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot) Mark Knecht
2006-11-25 20:48 ` Mick [this message]
2006-11-25 21:42 ` Mark Knecht
2006-11-25 22:49 ` Sergio Polini
2006-11-26 2:01 ` Mark Knecht
2006-11-26 2:59 ` Stroller
2006-11-26 19:01 ` Mark Knecht
2006-11-26 19:21 ` Stroller
2006-11-26 19:50 ` Mark Knecht
2006-11-26 13:13 ` Sergio Polini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200611252048.16847.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox