Piki

Forum Replies Created

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • in reply to: Problem booting in VirtualBox after install #19245
    Piki
    Member

    Hmm, even when using PIIX3, PIIX4, and ICH6 for my IDE setup in VirtualBox, it gives the same exact kernel panic.

    in reply to: Problem booting in VirtualBox after install #19244
    Piki
    Member

    VirtualBox automatically chose AHCI SATA for me, I will try installing it with IDE. Problem is, my only currently working machine is an AHCI SATA controller, so if this is not supported in openmamba, I will not be able to do a live install.

    in reply to: Problem booting in VirtualBox after install #19230
    Piki
    Member

    Apparently, it can’t access device dev(0,0) , nor can kinit find init . Also, it complains of something trying to access the hardware directly (this is a computer that doesn’t always have Internet access, my current Internet access is very intermittent).

    in reply to: Problem booting in VirtualBox after install #19228
    Piki
    Member

    The development snapshot yields the same result.

    in reply to: Cleanly upgrade to devel from stable #19107
    Piki
    Member

    This is a good chance to test the script. I’ll try it and report back. Should I also send my experiences to the developers mailing list?

    in reply to: No sound #19106
    Piki
    Member

    I sent the report, dmesg log, and relevant line from /var/logs/messages to reports@openmamba.org (I figured I may as well send them because this is where mambareport said to send it’s report).

    in reply to: No sound #19090
    Piki
    Member

    I just tried those, no luck either way.

    in reply to: [Solved] Sudden need for acpi=off to boot #19088
    Piki
    Member

    This is fixed by upgrading to the latest kernel in the stable repositories and adding the nongpl wireless backport added to stable not too long ago.

    in reply to: CUPS Browser Config not accepting password #19087
    Piki
    Member

    I am a part of the lpadmin group. I’m using 1.1 milestone 1.

    in reply to: Spare x86_64 box available for package builds #19072
    Piki
    Member

    If that would require restructuring code, I’m not the man for that as I’ve very little experience in coding anything. However, if all that requires is recompiling, I can help.

    in reply to: [Solved] BCM4310 Not Working #19063
    Piki
    Member

    That seems to have done the trick, except that my wireless card shows up as eth1 (and I thought that eth was short for Ethernet). But my wireless is working, so I’m happy.

    in reply to: [Solved] BCM4310 Not Working #19061
    Piki
    Member

    I unloaded the b43 and ssb modules via ‘modprobe -r’, then tried to modprobe the wl modules, and ended up with a fatal error telling me to check my dmesg, and the dmesg outputs the following error:

    [ 1634.711136] wl: Unknown symbol ieee80211_get_crypto_ops

    [ 1638.477869] wl: Unknown symbol ieee80211_get_crypto_ops

    [ 1696.047075] wl: Unknown symbol ieee80211_get_crypto_ops

    My lsmod would be attached if it would allow me to upload.

    in reply to: [Solved] BCM4310 Not Working #19042
    Piki
    Member

    If you can try to backport the driver, I’d appreciate it. If it can’t happen, then I’d be willing to upgrade to devel.

    in reply to: WiCD and dbus not connecting #19029
    Piki
    Member

    Thanks for the quick reply.

    It worked before on the LiveCD, so I removed the file you said, and it loads fine now, but when trying to connect to my network with the correct WPA2 Pre-shared Key, it fails to obtain an IP every time. I am using OpenMamba Milestone 1 v1.1.

    EDIT: So far, I’ve tried rebooting without my ethernet connected.

Viewing 14 posts - 1 through 14 (of 14 total)