Thanks: I used your number one Option and all is well. I did get some text during the boot about not being able to recognise pcie02 or something. It went by so fast it was hard to read it all. My Acer ONE will now recognize media cards when inserted after boot. Actually I now believe everything works on my Acer ONE. Even the WiFi switch will turn off/on the WiFi and the WiFi LEDs will blink on WiFi signal traffic. The onboard camera works. The speakers work, the earphone works. I believe that the Jaunty Jackalope 9.04 is a winner.
By-the-way everything works on my Acer Travelmate laptop, with the exception of the WiFi LED, which stays on ALL the time the computer is on, no matter whether or no the Wifi is on or off. And with 9,04 the WiFi switch will work like it was supposed to do. I also have two desktops using 9.04 (one is primary, the other a standby) Now for the personal stuff: Thanks to you and all of the Launchpad team that help us out here in the field to get our computers to work. I know I appreciate all the help I get from the Launchpad. One thing I have found is that when one person takes the time to send an email with good instructions, then I have gotten good results. Sometime the posts on the Launchpad assumes that everyone is as experienced and knowledgeable about Ubuntu GNU/Linux. John C-quel wrote: > Sorry I haven't been back for a few days. > > @dnl > > Sure, here is my information: > > Model: AOA 110-1698 (8.9") > BIOS: v0.3301 > SW: ubuntu-9.04-netbook-remix-i386.img > Status: exhibited issues until 'pciehp.pciehp_force=1' was used in the kernel > boot command. After this it worked perfectly, minus the display of extra > kernel messages during startup and during wake-up after suspend. > > > @John Hart > > Hi! Yes, if you apply the 'pciehp.pciehp_force=1' only during the Grub > edit screen it will only work that one time. This is good for testing, > but not great if you want to include that boot option permanently. > > The 'sudo vi' routine mentioned above works,... just as long as you know > how to use vi. I for one do not so I just prefer to use gedit (the real > name for "Text Editor"). :P > > Now as for how to modify the file in /boot/grub/menu.lst, I offer three > options. Pick the one you're most comfortable with. :) > > OPTION 1: > Open the Terminal via Accessories>Terminal and then type (or copy-n-paste) > the line "sudo gedit /boot/grub/menu.lst". It will likely prompt you for a > password. After which, the menu.lst file will open -- if you drop all the > way to the end of the file, you should see the boot options available (the > first line should start with something like "title Ubuntu 9.04, > kernel 2.6.28-11-generic"). > > You will want to append that code right after the kernel line, which > ends with "ro quiet splash" so that it becomes "ro quiet splash > pciehp.pciehp_force=1". Then save and reboot your Acer. > > > OPTION 2: > Same as OPTION 1, but instead of going through the Terminal, you can just > press ALT+F2 to bring up the Run window and type in "gksu gedit > /boot/grub/menu.lst" to open the file automatically. Or just put in "gksu > gedit" if you want to open the Text Editor with Root access only and then > navigate to /boot/grub/menu.lst yourself using File>Open. > > This is particularly handy if you don't like hanging around terminal > windows -- but by the sound of it, you don't seem like someone who's > afraid of the CLI. :) > > > OPTION 3: > This is a bit dangerous, but in the same ALT+F2 Run window, you can type in > "gksu nautilus". This will open up your file manager with Root Access. Here > you can navigate your entire system being able to add, edit, or delete > anything with absolute impunity. Just go to the /boot/grub folder, open > menu.lst, make your changes, save and you're done! :) > > Just be sure not to TOUCH anything else while in this mode as this is > the perfect environment to,... *cough cough*... accidentally delete your > one and only kernel. This is only recommended if you want the absolute > comfort of a GUI option, are very very careful, and/or want the > educational experience of navigating the inner recesses of your file > system. ;) > > > And that's all I can offer, the rest is up to you. Good luck! :) > > -- kernel does not detect card reader if card is inserted in reader before boot https://bugs.launchpad.net/bugs/271019 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
