Re: Network Configurator doesn't recognize Ndiswrapper in FC5

General Schvantzkoph wrote:

Also as to my original question, at one point FC's GUI recognized
Ndiswrapper devices (it might have been back in FC3 days). Have they
deliberately removed support for them or is it just a bug?

Maybe, please see;

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186664

I'm using some of the packages from the development site with CentOS-4.3,
among them are the system-config-network, udev and hal packages (all
recompiled from source). The GUI Network Configuration tool
(system-config-network-tui) does show my wireless (ndiswrapper) interface
as wlan0.

Again, I'm using (which is the same version as FC5);

$ rpm -qa --queryformat="%{n}-%{v}-%{r}.%{arch}.rpm\n"
'system-config-network*'
system-config-network-1.3.30-2.1.noarch.rpm
system-config-network-tui-1.3.30-2.1.noarch.rpm

Neither my /etc/modprobe.conf or /etc/modprobe.d/modprobe.conf.dist files
have an entry for my wlan0 device.

My hal and udev are a bit newer then FC5's however;

$ rpm -qa --queryformat="%{n}-%{v}-%{r}.%{arch}.rpm\n" 'hal*' 'udev*'
'pm-utils*' | sort
hal-0.5.7-5.i386.rpm
hal-0.5.7-5.x86_64.rpm
hal-devel-0.5.7-5.x86_64.rpm
pm-utils-0.17-1.i386.rpm
pm-utils-0.17-1.x86_64.rpm
udev-090-1.x86_64.rpm

Notice the pm-utils rpm packages which are needed for the newer hal
version(s). The pm-utils packages are power management utilities and
scripts.

Maybe a bug in hal or udev could be the problem????


--
"A personal computer is called a personal computer because it's yours,
Anything that runs on that computer, you should have control over."
Andrew Moss, Microsoft's senior director of technical policy, 2005
.

Relevant Pages

  • [Full-Disclosure] [RHSA-2003:064-01] Updated XFree86 4.1.0 packages are available
    ... security vulnerabilities have been found and fixed. ... other bug fixes, driver updates, and other enhancements have been made. ... Xterm, provided as part of the XFree86 packages, provides an escape ... Please note that this update is also available via Red Hat Network. ...
    (Full-Disclosure)
  • Re: Question re Debian versions
    ... > Then someone finds a bug in package A. It turns out to be an icky bug, ... graph involving the 13,000 or so packages in unstable is so complicated ... it should be a virtual distribution only ... It's also a real pain for maintainers because we get many bug reports ...
    (Debian-User)
  • Re: Reboot in output from "last":
    ... > be because at some point there was a bug in there, ... running, new network socket listeners, misbehaviour of normal commands, ... This is another reason to keep /usr for packages provided by the system ... with a proper firewall in place and minimal installation ...
    (comp.os.linux.security)
  • Re: Linux 2.6.25-rc1
    ... BUG: unable to handle kernel NULL pointer dereference ... tvaudio msp3400 bttv videodev v4l1_compat ir_common compat_ioctl32 ... the distfiles (source packages) are on a NFSv4 share. ...
    (Linux-Kernel)
  • [Full-Disclosure] SUSE Security Announcement: mc (SuSE-SA:2004:012)
    ... This update fixes a buffer overflow in shar while handling the '-o' ... New packages are available on our FTP servers. ... CAN-2004-0400 has been assigned to this bug. ...
    (Full-Disclosure)