On Mon, 4 Sep 2006, Dan Williams wrote:
On Mon, 2006-09-04 at 19:28 -0800, [EMAIL PROTECTED] wrote:
Dear James Cameron,
I did used version told by Jim on September 1:
vmlinuz-2.6.17-1.2608.olpc1
Also, I verified myself using 2.6.18-rc2
Both can boot via fedora with Marvell wireless support.
But if boot using slackware then Marvell wireless will not go up.
It will complain firmware did not exist.
It was too fast to conclude that this bug was fixed after you test it only
on fedora. I insist that it has problem under slackware.
Before this problem exist I see that under both fedora and slackware with
old BIOS do has problem on detecting Marvell wireless.
But after modprobe and rmmod it can solve the problem.
Now how many modprobe and rmmod cannot detect Marvell wireless under
slackware but work fine only under fedora only.
Ofcause I use the same kernel and modules on both system.
All modules and kernel under fedora got no problem but none of them can
made Marvell wireless to work any more under slackware.
The _kernel_ might be the same, but are udev and hotplug? The kernel
asks hotplug to get the firmware for it when a kernel module calls
request_firmware(), and those parts are more distribution-defined
because both udev and hotplug are entirely in user space. Make sure
that you also have the firmware in the same place that slackware thinks
it should be in.
Dan
Yes. udev and hotplug is my suspect and so far I cannot find out the
problem.
I don't know where fedora/slackware think where firmware should be. I will
try to find it out.
Before BIOS change both slackware and fedora know where is firmware
located correctly. I think it got info from BIOS.
Thank you.
supat
supat
On Mon, 4 Sep 2006, James Cameron wrote:
On Mon, Sep 04, 2006 at 02:51:51PM -0800, [EMAIL PROTECTED] wrote:
I will wait for new buildrom that cause no problem on Marvell wireless.
But this bug was fixed and closed!
http://dev.laptop.org/ticket/59
As of buildrom version 20060828-1.
What LinuxBIOS version did you use??
At this moment, I verify that current LinuxBIOS has problem on SLAKWARE
but no problem on fedora.
Why is Slakware a problem? Development is based on Fedora. What
happens? Have you logged a bug in trac yet?
--
James Cameron mailto:[EMAIL PROTECTED] http://quozl.netrek.org/
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
