Linux questions

[prometheus]

So I got a new laptop. I got ahold of my IT friend yesterday and we partitioned and loaded ubuntu. We got the video driver working but are still having problems with the WLAN and sound. Do you guys have any suggestions.

It's a Gateway 6752 with 2.99GB RAM (965 chipset), and the marvell Bigdog wireless card. We are using Ubuntu Gutsy.


MTA: This is my first experience with Vista.........It completely sucks ass. It took 3 hours of problem solving to load a video game on the windoz partition. My Spybot keeps pulling up System Startup global entry value deleted, WTF is this about? I deleted all the Internet explorer stuff, could that be the source.

[thod]

More info needed.

Linux problems need you know what you have. Check through the boot logs and see if the drivers are loaded. The install package hopefully recognised your hardware and copied the drivers from the CD to hard disk and configured your kernel to load them. Cant say though

Your Vista problem sounds like you have got your anti spyware set up to monitor registry changes. Some software insists on changing the value to what it already was every time. Just set it to allow it to do so. You are watching for things you dont expect changing registry values since that indicates malware.

[pavman]

Hey.... As for Linux:
Do you know what chipset your wireless card uses? There's basically 3 chipsets out there... can't remember them off hand, you might try the madwifi driver if its an atheros-based chipset.

I know the others have them as well, but I got that working pretty slick in 03 or so when the driver was still pretty piss-poor beta.

I need more info too, like what's the wifi card's make and model/model number (model number is key)?

Since its laptop based, you'll need the pcmcia drivers as well to sit below the driver level of your wifi card. I'm assuming ubuntu did some of this for you, but its always difficult to remotely help someone w/o directly talking them through it.

Ok...
0. ls /var/log/boot ... if this isn't here, I recommend turning on bootlogd
1. Check if bootlogd is setup, if not turn it on via:
vi /etc/bootlogd and change
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=No

to yes. Save, reboot (init 6)

You should see something like PCMCIA blah blah blah OK.

We need to confirm:
1. PCMCIA driver is loaded
2. your network card driver is loaded (if not, might have to re-install w/ the driver or re-build the kernel with the driver, or build/install the driver as a module... your choice).

Get the card make/model #, we can go from there.

Also...is this a wireless card? IE, not just wifi? I looked up marvell, and it looks like they have a wide range of products.

[prometheus]

:scared:

Damn, I need to talk with my IT friend, I'll get the facts and post them in a little bit. Thanks guys.

[HackerX]

The other option you can try is this:
To view links or images in this forum your post count must be 2 or greater. You currently have 0 posts.

"This project implements Windows kernel API and NDIS (Network Driver Interface Specification) API within Linux kernel."

Worked for me last time I used it

[prometheus]

The other option you can try is this:
To view links or images in this forum your post count must be 2 or greater. You currently have 0 posts.

"This project implements Windows kernel API and NDIS (Network Driver Interface Specification) API within Linux kernel."

Worked for me last time I used it

I'm pretty sure we loaded a ndiswrapper, that fixed our problems last time with Fedora 6.

[pavman]

Joomla might work.

If you feel comfortable going that route, go for it. I noticed Marvell has drivers on its site for Linux, so it might be better to go w/ their drivers and not a generic windows wrapper driver (depends on what functionality you need...I find generic drivers don't always exploit all of the features of the hardware).

I'd recommend going with a native Linux driver if you can, rather than an NDIS wrapper.

Here's what I see on Marvell's site: To view links or images in this forum your post count must be 2 or greater. You currently have 0 posts.

Although it seems to be generic for Yukon devices. Again, if you look up the model on their site, you might just find a driver for your specific card for Linux. :o)

[prometheus]

Joomla might work.

If you feel comfortable going that route, go for it. I noticed Marvell has drivers on its site for Linux, so it might be better to go w/ their drivers and not a generic windows wrapper driver (depends on what functionality you need...I find generic drivers don't always exploit all of the features of the hardware).

I'd recommend going with a native Linux driver if you can, rather than an NDIS wrapper.

Here's what I see on Marvell's site: To view links or images in this forum your post count must be 2 or greater. You currently have 0 posts.

Although it seems to be generic for Yukon devices. Again, if you look up the model on their site, you might just find a driver for your specific card for Linux. :o)

My IT friend is going to stop by in a few hours that link looks promising.

[Vortex]

Good luck. Linux and wireless drivers is a minefield... Probably the only really WTF? issue linux has besides getting proprietary graphics systems to work.

[HackerX]

Joomla might work.

If you feel comfortable going that route, go for it. I noticed Marvell has drivers on its site for Linux, so it might be better to go w/ their drivers and not a generic windows wrapper driver (depends on what functionality you need...I find generic drivers don't always exploit all of the features of the hardware).

I'd recommend going with a native Linux driver if you can, rather than an NDIS wrapper.

Here's what I see on Marvell's site: To view links or images in this forum your post count must be 2 or greater. You currently have 0 posts.

Although it seems to be generic for Yukon devices. Again, if you look up the model on their site, you might just find a driver for your specific card for Linux. :o)

Oh absolutely, if you can find native drivers for your card go with it. Just use ndiswrapper as a fall back if you can find nothing else (which is unfortunately still common with wireless cards these days).