Hardy Heron beta random crash

[jaarik]

I know this forum might be too general for posts like this. Just being curious, if anybody running Unubtu 8.04 beta has experienced VERY random kernel lock-ups using Ndiswrapper.

By random I mean anything from 5 minutes to 1 day into the session before the crash occurs with no traces whatsoever in any of the system logs.

 

[Kasyx]

Hence the "Beta" part

Go check out http://launchpad.net/ubuntu

 

[w1z4rd]

ndiswrapper is used to load windows drivers... so.. you are loading windows drivers onto a beta linux system. w00t!

Is /var/log/messages telling you anything?

 

[Skeptik]

ndiwrapper is used to load windows drivers... so.. you are loading windows drivers onto a beta linux system. w00t!

Is /var/log/messages telling you anything?

Yes, if Linux provided such drivers for wireless networking you wouldn't need to use wrappers. t00w

 

[w1z4rd]

Yes, if Linux provided such drivers for wireless networking you wouldn't need to use wrappers. t00w

Dude, you seriously have no idea what you are talking about. So what .. microsoft writes the drivers for their hardware vendors? Dont be daft. Yurre. Hardware vendors write the drivers, and when they are locked in with MS (anti-comp) they dont write the drivers for linux.. then the linux community has to try make it themselves or use ndiswrapper to try use the drivers written by the vendor for MS.

I can see you are going to be as reasonable here in this section as you were in the Vodacom section. Trolling with little knowledge.

 

[fskmh]

Yes, if OEMs provided information to kernel developers and 3rd party driver developers you wouldn't need to use wrappers. t00w

Fixed that for you .

http://ndiswrapper.sourceforge.net/joomla/

NDISwrapper
Written by giri
Friday, 27 April 2007
Many vendors do not release specifications of the hardware or provide a Linux driver for their wireless network cards. This project implements Windows kernel API and NDIS (Network Driver Interface Specification) API within Linux kernel. A Windows driver for wireless network card is then linked to this implementation so that the driver runs natively, as though it is in Windows, without binary emulation.

With ndiswrapper, most miniPCI (builtin), PCI, PCMCIA (Cardbus only) or USB wireless network cards work in Linux with x86 or x86-64. Although ndiswrapper is intended for wireless network cards, other devices are known to work: e.g., ethernet cards, USB to serial port device, home phone network device etc.

For help with installation / troubleshooting etc., see Documents and/or Help accessible from the main menu. IRC at irc.freenode.net #ndiswrapper is not very active, but occasionally someone there may be able to help you.

 

[jaarik]

ndiwrapper is used to load windows drivers... so.. you are loading windows drivers onto a beta linux system. w00t!

Is /var/log/messages telling you anything?

Nope. The system is completely unaware. No traces there, as I said. kernel freezes, no time to panic! LOL

 

[Skeptik]

Fixed that for you .

I think both versions can coexist, seeing that neither are wrong, despite some irrational and irrelevant comments

@wizford (Vodacom) where does that fit into Linux wrappers?? or u havin a go again dude?

The problem with wrappers is that they can be quite finicky (version specific?)

 

[fskmh]

I think both versions can coexist, seeing that neither are wrong, despite some irrational and irrelevant comments

Was your generalisation rational? Intel now provide drivers and firmware for their wireless cards, granted that ipw drivers were available long before that. Here's a list of Linux drivers:

http://ipw2200.sourceforge.net/ -- Previously used for Intel etc., now iwl seems to be recommended, also no regulatory daemon required with iwl driver.
http://acx100.sourceforge.net/ -- Used for D-Link etc.
http://rt2x00.serialmonkey.com/wiki/index.php?title=Main_Page -- used with rt2500 and others, which I am using on this desktop right now. Performance is much more reliable than the Windows driver BTW.
http://madwifi.org/ -- Used for Netgear etc, I used a WG511T in my old laptop with this driver, also performed more reliably than the Windows driver.

Still think your comment is valid?

The problem with wrappers is that they can be quite finicky (version specific?)

Broadcom should be avoided because they are one of the culprits of what I quoted above with the NDISwrapper link. I have used one in an HP NX6125 with no problems, apart from trying to find the 64 bit driver to extract the .inf file, of course .

I think most problems are related to ACPI issues (powersaving) or firmware.
@jaarik, see if you should be using updated firmware with Ubuntu 8.04 beta.