| 1 |
On Fri, Sep 24, 2010 at 3:43 PM, Enlightened User <linux@×××××.com> wrote: |
| 2 |
> On Sep 24, 2010, at 4:30 PM, Mark Knecht wrote: |
| 3 |
> |
| 4 |
>> On Thu, Sep 23, 2010 at 10:04 PM, Joseph Jezak <josejx@g.o> wrote: |
| 5 |
>>> |
| 6 |
>>> My responses are inline this time. It's easier when there's so much |
| 7 |
>>> going on! |
| 8 |
>>> |
| 9 |
>>> On 09/23/10 16:41, Mark Knecht wrote: |
| 10 |
>>>> |
| 11 |
>>>> Two pictures posted: |
| 12 |
>>>> |
| 13 |
>>>> Top half of boot screen: |
| 14 |
>>>> http://www.flickr.com/photos/29328985@N03/5018717650/ |
| 15 |
>>>> |
| 16 |
>>>> Bottom half of boot screen |
| 17 |
>>>> http://www.flickr.com/photos/29328985@N03/5018718202/ |
| 18 |
>>>> |
| 19 |
>>> |
| 20 |
>>> Okay, these look exactly as expected. You've booted into the shell fine |
| 21 |
>>> and the kernel does detect the hard drive fine. It appears that the disk |
| 22 |
>>> was not cleanly unmounted, which is what the messages in the bottom |
| 23 |
>>> picture indicate. Once you get USB working so we can type into the |
| 24 |
>>> console, we'll take a look at what's actually going on. |
| 25 |
>>> |
| 26 |
>>>> Full USB HID support is built as modular. I don't seem to be able to |
| 27 |
>>>> change it to built in. make menuconfig is only giving me modular or |
| 28 |
>>>> not set. (Kernel config USB info this is set is at the end) |
| 29 |
>>> |
| 30 |
>>> If you use menuconfig and you go to the "Help" option, it will tell you |
| 31 |
>>> what dependencies need to be set in order to build the module. Most |
| 32 |
>>> likely, you did not set the USB subsystem itself to be built in. |
| 33 |
>>>> |
| 34 |
>>>> lspci says the controller is an Apple controller and the driver is |
| 35 |
>>>> 'macio' which seems sensible. I see it in the boot screen I think. |
| 36 |
>>>> That driver is built in, but the PATA_MACIO driver is not: |
| 37 |
>>>> |
| 38 |
>>>> (chroot) livecd linux # cat .config | grep MACIO |
| 39 |
>>>> # CONFIG_PATA_MACIO is not set |
| 40 |
>>>> CONFIG_ADB_MACIO=y |
| 41 |
>>>> (chroot) livecd linux # |
| 42 |
>>>> |
| 43 |
>>>> Maybe I've mistakenly left the right disk driver out of the kernel |
| 44 |
>>>> thinking the hardware was SATA based? Does the PATA_MACIO option need |
| 45 |
>>>> to be set for the Mac Mini? I don't understand how this kernel config |
| 46 |
>>>> would have ever worked befor unless I'm confusing where it came from. |
| 47 |
>>>> |
| 48 |
>>> |
| 49 |
>>> You're using the old style driver which results in devices named hdX#. |
| 50 |
>>> It's called IDE_PMAC. The new driver which uses the sdX# naming |
| 51 |
>>> convention (and uses libpata), is called PATA_MACIO. |
| 52 |
>>> |
| 53 |
>>>> Does the append="init=/bin/bash" command allow the kernel to load |
| 54 |
>>>> drivers or do I need to build USBHID into the kernel to get the |
| 55 |
>>>> keyboard to work at this level of boot? |
| 56 |
>>> |
| 57 |
>>> I would built it in for now, it'll be easier since there's no good way |
| 58 |
>>> to get into the system to tell it to load the drivers. |
| 59 |
>>> |
| 60 |
>>> -Joe |
| 61 |
>>> |
| 62 |
>>> |
| 63 |
>> |
| 64 |
>> Hi Joe, |
| 65 |
>> OK - I got USB working and with the append="init=/bin/bash" in I |
| 66 |
>> can at least do cd and ls commands. |
| 67 |
>> |
| 68 |
>> All the devices you asked about exist - /dev/hda1 through 20, |
| 69 |
>> /dev/hdb1 through 20, /dev/null and /dev/zero - all exist. |
| 70 |
>> |
| 71 |
>> Doing know if it's a clue but in this append="init=/bin/bash" |
| 72 |
>> state I was unable to do a reboot or a shutdown as it complained about |
| 73 |
>> missing initctl I think? |
| 74 |
>> |
| 75 |
>> Being that I made a number of changes to the kernel config to get |
| 76 |
>> USB working I remove the append line from yaboot.conf and tried |
| 77 |
>> booting into Gentoo proper but it's still stopping at the same place |
| 78 |
>> with the same message about no mtab file. |
| 79 |
>> |
| 80 |
>> I'll put the append back in and wait for further ideas. |
| 81 |
>> |
| 82 |
>> Thanks for sticking with me! |
| 83 |
>> |
| 84 |
>> Cheers, |
| 85 |
>> Mark |
| 86 |
>> |
| 87 |
> Assuming you are still stopping near: |
| 88 |
> fsck.ext3... |
| 89 |
> |
| 90 |
> Can you confirm that /sbin/fsck.ext3 exists? |
| 91 |
> If not, then emerge e2fsprogs. |
| 92 |
> |
| 93 |
> Barry |
| 94 |
> |
| 95 |
> |
| 96 |
|
| 97 |
The chroot is currently doing an emerge -e @world so I've shelled into |
| 98 |
the machine and am showing from that perspective. All the typical fsck |
| 99 |
programs are there and I rebuilt e2fsprogs a couple of days ago. |
| 100 |
|
| 101 |
|
| 102 |
livecd gentoo # ls /mnt/gentoo/sbin/fsck* |
| 103 |
fsck fsck.ext2 fsck.ext4 fsck.minix |
| 104 |
fsck.cramfs fsck.ext3 fsck.ext4dev |
| 105 |
livecd gentoo # |
| 106 |
|
| 107 |
When emerge -e @world completes I'll give it a reboot but somehow I |
| 108 |
don't have much faith that it will have fixed anything. Right now I |
| 109 |
feel it's either something missing from my kernel config, or some |
| 110 |
critical install step that I keep missing because of the way I read |
| 111 |
the document and maybe some step that listed inside a paragraph |
| 112 |
instead of being called out in purple like most of them are. (They are |
| 113 |
in there, like the locale-gen step and a few others...) |
| 114 |
|
| 115 |
I'll check back later when the rebuild is complete. |
| 116 |
|
| 117 |
Thanks! |
| 118 |
|
| 119 |
Cheers, |
| 120 |
Mark |
Archives