(sorry to resurrect an ancient thread, I just ran into this and had to resolve it as well, and the solution wasn't posted here and I couldn't find the right answer anywhere)

Two of the ebuilds in the python dep-chain for Cura do not seem to honor the python versions listed/specified in eselect ...

This sounds like the system is detecting the wrong backlight control by default. If you can ssh in, try poking at things in /sys/class/backlight/*/brightness to see if anything can get the screen to turn on. There may be 2 different entries there (one like nv_backlight, and one like acpi_backlight ...

That depends on which MacBook Pro Facetime HD Camera...

If it's one of the USB ones, odds are 'fairly high' that it will either work out of the box, or with USB IDs added to the correct driver.

If it's the pci-e one (in newer models), there's not yet a working driver. Here's the 'ongoing work ...

There is a chance that a bug was discovered in one of the hardware acceleration branches in kernel for your card and some feature has been disabled. What exact hardware is it (lspci output), and kernel dmesg output might provide some insight into the problem. Have you booted into the old kernel to ...

I have a few sd cards that behave somewhat like this. What I end up having to do is unplugging and replugging it from the adapter a few times (the adapter/card just don't get along). It's especially common when I use 1 particular microsd to sd adapter.

Did you receive the laptop? Does hotplug/unplug work? Determining there IS a problem is the first step

I would add, at the beginning of each init.d script's start section:

echo Scriptname
date

to see if one particular script is screwing with it. If the first script to start has the problem, it's either in your initrd or some kernel driver mucking with it. If you find that it's a particular script ...

After getting wireless modules loading, you still need to manage the wireless. wpa_supplicant is pretty much the bare minimum to get it working, but also using something like network-manager, wpa-gui, or wicd to configure wpa_supplicant is also likely going to be useful. Other than WEP or Open ...

I don't think the kernel is booting, the environment is a busybox shell, so the initramfs has started but not started the kernel
Edit:I should have said an ash shell with the busybox tool kit.

To help you understand what goes on:

1. Bios boots bootloader after basic hardware configuration
2 ...

Ok, now I am really nervous. I have a thunderbolt monitor which I will be using as a) the main display and b) gigabit ethernet and USB hub. I also have a stand-alone thunderbolt ether net adapter (apple).

I have a MacBook Air also, which I could try and do the thunderbolt ad hoc networking as well ...

I didn't want to suggest embedding it directly..... but....

It's exactly what I do. There's a problem with rebuilding kernels with embedded initramfs, here's the patch I've been using for years:


diff --git a/usr/Makefile b/usr/Makefile
index e767f01..041333b 100644
--- a/usr/Makefile
+++ b/usr ...

I've been following the linux ACPI and linux PCI mailing lists for a few years and read a lot of the thunderbolt discussions. The biggest topic of contention as far as support has been the fact that, on Macs, the EFI/BIOS stuff doesn't correctly setup the thunderbolt hardware in cases where it doesn ...

Yes, that was it. Thanks for the help debugging this issue. I thought I would be clever and symlink the files needed for the initramfs so that I was sure to always have the current version. Obviously, that did not work. Would hard links accomplish that goal, or is it better to just use a ...

So thinking about this a bit, the problem isn't related to your init script. Your boot process isn't getting that far.

Following is what my init script currently looks like, though this is one of a couple dozen different permutations I have tried.
[code="su -p -c "find . -print0 | cpio --null -ov ...

your error code (-40) looks like it could be:

#define ELOOP 40 /* Too many symbolic links encountered */

So I bet you have some broken symbolic links once you consider that the top level of your init tree becomes / in initramfs.

The output of:

for f in $(find -type l); do ls -l $f; done ...

Comparing your initrd to mine (ignoring the structural differences), you don't specify a mount point when you mount the gentoo named partition:


/bin/mount -o ro `findfs LABEL=gentoo` || rescue_shell "Problem mounting root. Dropping to shell"


vs


mount -o ro $(findfs "$dev") /mnt/root >>/tmp ...

Is there any chance you're missing the devicemapper or raid modules in your kernel? If you compiled them as modules and put them in your init.d, you would probably need to manually insmod them.

Ok, snagged bash and bzip2 binaries out of a stage3. That got emerge working again, did a lot of testing and narrowed it down to gcc. gcc seems to have been outputting badness. Switching to an old gcc resolved it.

After upgrading a few packages (bzip2, and bash are highly suspect...) I'm now getting this:


/etc/portage # emerge -1 bash
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-shells/bash-4.2_p45-r1
/usr/lib64/portage/bin/ebuild.sh: line 719: 5282 ...

What graphics card/driver are you using? This looks, very much, like FF is trying to use a GPU Accelerated Rendering method that isn't properly supported by your hardware/driver.

Thanks for the bashrc pointer. I was able to achieve what I needed with:


eecho() {
[ "$NOCOLOR" = "false" ] && echo -ne '\e[1;34m>\e[1;36m>\e[1;35m>\e[0m ' || echo -n ">>> "
echo "$*"
}

pre_src_compile() {
eecho "Ramping up fans"
echo level full-speed > /proc/acpi/ibm/fan
}

post_src_compile ...

Is there any built in facility to have emerge run a script/command when a emerge is starting/finishing?

---

Back story: I have a poorly designed lenovo w510 that overheats. While I battle with Lenovo about getting it repaired (again and again and again), I've found that forcing the fan on full ...

Etal wrote:Did you forget to rebuild cloog-ppl?

Code: Select all

 * After an upgrade of PPL it is important that you rebuild
 * dev-libs/cloog-ppl.

At least for me, it'd fail to build with the new toolchain.

geki wrote:interesting
yes, I look for a maintainer of the boost dependend packages.
no idea what to do about rb_libtorrent[python]. patches are welcomed!

Is it failing for you as well? I didn't dig into it because I figured it was something specific to my bastardized system.

Some more anecdotes from your overlay:

rb_libtorrent-0.15.8 is failing to build for me with USE="python"
qbittorrent-2.8.5 is failing to build for me with rb_libtorrent < 0.15.8 || rb_libtorrent = 0.15.8 USE = -ssl

IE:

qbittorent 2.8.5 requires at least 0.15.8(+ssl)