1 |
On 09/25/10 07:45, Mark Knecht wrote: |
2 |
> On Thu, Sep 23, 2010 at 10:04 PM, Joseph Jezak <josejx@g.o> wrote: |
3 |
>> My responses are inline this time. It's easier when there's so much |
4 |
>> going on! |
5 |
>> |
6 |
>> On 09/23/10 16:41, Mark Knecht wrote: |
7 |
>>> Two pictures posted: |
8 |
>>> |
9 |
>>> Top half of boot screen: |
10 |
>>> http://www.flickr.com/photos/29328985@N03/5018717650/ |
11 |
>>> |
12 |
>>> Bottom half of boot screen |
13 |
>>> http://www.flickr.com/photos/29328985@N03/5018718202/ |
14 |
>>> |
15 |
>> Okay, these look exactly as expected. You've booted into the shell fine |
16 |
>> and the kernel does detect the hard drive fine. It appears that the disk |
17 |
>> was not cleanly unmounted, which is what the messages in the bottom |
18 |
>> picture indicate. Once you get USB working so we can type into the |
19 |
>> console, we'll take a look at what's actually going on. |
20 |
>> |
21 |
>>> Full USB HID support is built as modular. I don't seem to be able to |
22 |
>>> change it to built in. make menuconfig is only giving me modular or |
23 |
>>> not set. (Kernel config USB info this is set is at the end) |
24 |
>> If you use menuconfig and you go to the "Help" option, it will tell you |
25 |
>> what dependencies need to be set in order to build the module. Most |
26 |
>> likely, you did not set the USB subsystem itself to be built in. |
27 |
>>> lspci says the controller is an Apple controller and the driver is |
28 |
>>> 'macio' which seems sensible. I see it in the boot screen I think. |
29 |
>>> That driver is built in, but the PATA_MACIO driver is not: |
30 |
>>> |
31 |
>>> (chroot) livecd linux # cat .config | grep MACIO |
32 |
>>> # CONFIG_PATA_MACIO is not set |
33 |
>>> CONFIG_ADB_MACIO=y |
34 |
>>> (chroot) livecd linux # |
35 |
>>> |
36 |
>>> Maybe I've mistakenly left the right disk driver out of the kernel |
37 |
>>> thinking the hardware was SATA based? Does the PATA_MACIO option need |
38 |
>>> to be set for the Mac Mini? I don't understand how this kernel config |
39 |
>>> would have ever worked befor unless I'm confusing where it came from. |
40 |
>>> |
41 |
>> You're using the old style driver which results in devices named hdX#. |
42 |
>> It's called IDE_PMAC. The new driver which uses the sdX# naming |
43 |
>> convention (and uses libpata), is called PATA_MACIO. |
44 |
>> |
45 |
>>> Does the append="init=/bin/bash" command allow the kernel to load |
46 |
>>> drivers or do I need to build USBHID into the kernel to get the |
47 |
>>> keyboard to work at this level of boot? |
48 |
>> I would built it in for now, it'll be easier since there's no good way |
49 |
>> to get into the system to tell it to load the drivers. |
50 |
>> |
51 |
>> -Joe |
52 |
>> |
53 |
>> |
54 |
> Hi Joe, |
55 |
> OK, I finished the emerge -e @world. No changes. Still doesn't boot. |
56 |
> |
57 |
> I've put the append="init=/bin/bash" back in and booted. I'm at the |
58 |
> console and this is confusing. It seems that /dev/hda4 is probably |
59 |
> mounted. I can do |
60 |
> |
61 |
> ls -al / |
62 |
> |
63 |
> I see all the stuff I'd expect to see - /bin, /boot, etc. - and also |
64 |
> the two downloads necessary to do the install - portage-latest.tar.bz2 |
65 |
> & stage3-ppc-20100919.tar.bz2 - so I must be looking at the right |
66 |
> physical hard drive. |
67 |
> |
68 |
> However even though I see that stuff simple commands like df don't |
69 |
> work yielding something like this: |
70 |
> |
71 |
> (none)/ #df |
72 |
> df: cannot read table of mounted file systems: No such file or directory |
73 |
> |
74 |
> Additionally, there is nothing at all under /proc. It's empty! |
75 |
> |
76 |
> Cheers, |
77 |
> Mark |
78 |
> |
79 |
> |
80 |
None of these things are weird, they're expected! |
81 |
|
82 |
When you start the system with "init=/bin/bash", the only thing your |
83 |
system does is start bash as the only process. Things like mounting |
84 |
proc, remounting the root file system r/w (and setting up mtab) aren't |
85 |
done because they're part of the normal startup process. |
86 |
|
87 |
Can you run fsck.ext3 from the shell that starts when you replace init? |
88 |
|
89 |
Also, which version of udev are you using? I forgot to ask if you're |
90 |
running ~ppc instead of ppc, you may want to try switching to the |
91 |
PATA_MACIO driver in order for the system to work properly. |
92 |
|
93 |
-Joe |