On Sun, 7 Apr 2002, Justin Christopher wrote:
> Modem on the iBook2/500 does not work. This is fixable > by tweaking the PPP modem timeout values. These values > are known, but this fix has not been applied to the > installer. Thus, even though the fix is known, the > installer still puts in PPP values that will not work. > OK - I'll see if I can do this in the installer, or patch kppp. > > Sleeping an iBook2 by closing the lid or using the > 'snooze' command does not work. When you awaken the > computer, it does not accept keyboard or mouse input. > Colin Ward has the same problem so it's not just me. > OK, so should I go buy an ibook2 so I can reproduce it? All I can really do is apply a patch, if you know of one. I also built the newest pmud and pointed Colin to it. > By default the CDROM drive cannot be opened by right > clicking (no permissions), nor by clicking the > keyboard eject key. I bet 90% of people who complete > the install process can't figure out how to put > another cd in to install more packages without a trip > to google. Frankly, in a modern GUI I don't feel I > should have to open a terminal and type "cd mnt/cdrom, > eject" to open a cd rom drive! > OK - verified. I guess I never thought to check this as there really isn't anything PPC specific about ejecting a CD, but in just trying it now in KDE, it just sits there. It's not a permissions issue, or you wouldn't be able to do it from a terminal either. It's a fairly well know bit of information that the Apple function keys in general don'tperform their functions in Linux without additional software such as ikeyd. > There is a known problem with selecting "do you want > to start the connection at boot" in the installer. > This is a huge bug, and you blew me off by saying "I'm > not familiar with this" despite the fact that I > provided you with an outline of steps to reproduce the > problem. > I didn't blow you off and in fact spent several hours last week trying to reproduce the scenario, and never did hit a screen asking me that question. It must only happen when setting up 2 interfaces. I saw a review of x86 that mentioned a similar situation, so indeed it does seem to exist. In the case of 2 interfaces, it sort of makes sense to ask, as you wouldn't eant to start both up, unless they are connected to different subnets. > If the user says "yes" to "Do you want to start this > connection at boot?" a line shows up in the boot > process called "checking for internet connections to > start at boot". This line appears after "getting IP > info for eth0" and "getting IP info for eth1". If > getting IPs fails, the boot process will hang on the > "checking for internet connections to start at boot" > line forever. > > To my knowledge that problem has not been addressed, > despite the fact that it can easily cause a newbie to > end up with an unbootable system. > > Gnome is so unstable I would not call it usable. I do > not experience this problem on x86, so something else > is wrong. > Gnome in general or the control-center/bononbo-moniker issue? I haven't seen any other crashes in gnome. > It's my opinion that a PPC-specific distribution > should offer to configure an Apple Airport card during > the install. They are all the same, there is only one > driver - there should be a prompt for network name, > encryption key, password, and whatever else is needed > to connect. > OK, I agree it woould be a nice feature, but at some point you have to stop adding features and say this iteration is done, or you'll never finish. I already have people upset that we don't have gnome2 or kernel-2.4.x. > In the installer, why should the user have to choose > between OHCI and UHCI USB interfaces? I only know I > have USB, I don't even know what those are? At this > point in the installer, you have already autodetected > my USB mouse, so shouldn't the installer know what to > load? > This question isn't asked at all in recommended install. If you choose expert install a lot of additional questions are posed. > Finally, I still feel strongly that DHCP should be > able to retrieve IPs from an Apple Airport base > station after the default install (especially on a > Mac-specific distribution) although I understand your > position about not worrying too much about a specific > piece of hardware. > I'd love this to work too. I really don't like to have unhappy users, but I can't afford to go out and secure each piece of hardware to do hardware testing. dhcp is general does work, I know that for a fact as I use it every day. > When I installed RedHat 7.2 on a Dell Inspiron, > everything worked flawlessly with no post-install > tweaking. I would like to see PPC reach that level > (especially since there are only a couple hardware > types to support, it would seem to be possible). But > it is not there yet. > I guess we see things through different eyes. I know Linux on PPC is not fully there yet. I'm trying to do what I can to help that situation, but it's not going to happen overnight. People mistakenly think Apple machines should be easy, that the hardware is all the same, but that's very untrue. You should see that from the grief we're having trying to X working properly on a handful of ATI cards. You should also see that from the people talking about kernel panics with mac53c94, when I can load up the same kernel/driver on a 7600 with no issue. I see plenty of horror stories on the x86 side too, and have experienced them myself. I don't think any OS is going to be flawless on every piece of hardware out there. That said, I do appreciate any feedback that's given here. Sometime's the timing's not right to fully address the issue, but I do what I can. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
