[Silvan]

Test

[Silvan]

Test

[Silvan]

Text

[Silvan]

Text

[Silvan]

At the moment there is just an experimental script

[Silvan]

Maybe there is some hint for the problem in /var/log/messages or in the dmesg log. You can also send a report for me to analyze it (go to KDE Menu -> system -> openmamba -> Generate a system report.

[Silvan]

First make sure that you have tried all the mixer buttons and sliders. Then you can try installing kernel-mamba-sound-backport or kernel-mamba-sound depending on what you have currently installed to replace it.

[Silvan]

I’ve seen the problems with wineasio, too, while installing Sibelius on openmamba for a customer. I finally made it work without wineasio, so I didn’t investigate further, but when I have time I will do some more tests on this, if nobody else comes first. Thanks for testing openmamba and reporting this problem.

[Silvan]

Yes, the interface should be renamed to wlan* for this driver. Maybe this will be done upstream by driver developers in future, at the moment I’ve recently fixed udev to keep persistent interface naming so that eth0 and eth1 are not swapped after reboot and that should solve the first need of having working network connections from the user point of view.

[Silvan]

Piki, first of all thanks for your offer to contribute to this project.

Porting openmamba to the x86_64 architecture requires first some not trivial work on the gcc/glibc toolchain, and having or getting experience on this would be necessary. The x86_64 glibc is available for cross-compilation (package is cross-x86_64 glibc) and one of the first things to do would be creating multilib (x86 and x86_64) glibc for the x86_64. If you are interested in this development, I can provide a x86_64 kernel build and I would suggest you to subscribe to the openmamba-devel (english language) mailing list (see http://www.openmamba.org/lists/) for further discussion.

[Silvan]

Thanks for your suggestion. Swami will be packaged and evaluated for the future versions of openmamba.

[Silvan]

I’ve recently seen this problem on 1.1 too. I think it is now fixed with an update of kernel-mamba-nongpl-wl that will be available in 1-2 hours, or you can fix it yourself by replacing package kernel-mamba-wireless-backport with kernel-mamba-wireless and rebooting.

If you can cable-connect just do:

sudo apt-get install kernel-mamba-wireless

[Silvan]

The driver is now available in milestone1 1.1. You need to install the package kernel-mamba-nongpl-wl. Make sure that the module (wl.ko) gets loaded in place of the b43 and b43legacy modules.

[Silvan]

In devel this is currently supported by the broadcom_sta module, If you use the stable release you might want to upgrade or I’ll see if the driver can be backported.

[Silvan]

Probably the Flash-1GB media has a problem after desktop user login. I’m not too surprised by this because as I said this media hasn’t been tested for months.

The bootusb method is more often tested, so I would suggest to try to solve the problem here. First, did you try with stable (livecd/installdvd/livegames/livestudio+bootusb) or devel (livecd/livedvd/livegames+bootusb) version? As Ercole said first ensure that you are using the same version for the iso media and the bootusb archive. Then when you boot you can select the “Debug” choice to get information on where the boot problem is.

[Author]

Posts