(** Originally posted to freebsd-current@freebsd.org but I noticed that there are 9.0 RC3 questions here on freebsd-stable; I am not sure which forum is appropriate. **) I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9. The machine no longer boots. However, if I put hint.acpi.0.disabled=1 in /boot/loader.conf then the machine runs fine. With RELENG_8 the machine had no loader.conf, and the power button worked on my desktop machine. Now with ACPI disabled my power button does not work. I have found that the machine hangs at boot during a scan of the PCI bus, but if I disable that (hw.acpi.disable=pci) then the machine cannot find a boot drive. So I have lost functionality that worked fine in BSD 8. Thoughts? Suggestions? Thanks, Dan Allen
On Sat, Dec 31, 2011 at 10:26:09AM -0700, Dan Allen wrote:> (** Originally posted to freebsd-current@freebsd.org but I noticed that there are 9.0 RC3 questions here on freebsd-stable; I am not sure which forum is appropriate. **) > > I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9. The machine no longer boots. However, if I put > > hint.acpi.0.disabled=1 > > in /boot/loader.conf then the machine runs fine. With RELENG_8 the machine had no loader.conf, and the power button worked on my desktop machine. Now with ACPI disabled my power button does not work. I have found that the machine hangs at boot during a scan of the PCI bus, but if I disable that (hw.acpi.disable=pci) then the machine cannot find a boot drive. > > So I have lost functionality that worked fine in BSD 8.Do you have a necessary reason to upgrade to 9 given this situation? Given the conditions I would stay you should stay with 8.> Thoughts? Suggestions?Provide full output from a verbose boot so developers can try to figure out where the problem is. You will either need serial console or firewire console for this task, as the amount of text will be too much to type in (many, many screens worth). Simply showing a photo of the last screen where it locks up may not be sufficient. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
On 31 Dec 2011, at 10:57 AM, Jeremy Chadwick wrote:> Do you have a necessary reason to upgrade to 9 given this situation? > Given the conditions I would stay you should stay with 8.This philosophy seems wrong, but it may be the way to go. My Toshiba Satellite U205 used to work great with RELENG_7, but the boot code of RELENG_8 will not recognize the 2nd core of my Core Duo (not Core 2 Duo) processor. Nobody seems to care as few machines have Core Duo, or few people use this era of Toshiba BIOS, or whatever. Now my Dell GX270 ACPI code is pre 2.0 (so Garrett tells me), so RELENG_9 is out. I guess I should run all of my older machines on RELENG_7 but -- and this is where the philosophy you suggest seems wrong -- I still want the latest apps, security fixes, etc. If the stable tree updates ls or tcsh or awk, I want these, but the core OS seems to have moved on from 2004 machines. In other words, there is no tree for me. Dan
On 31 December 2011 11:41, Dan Allen <danallen46@airwired.net> wrote:> My Toshiba Satellite U205 used to work great with RELENG_7, but the boot code of RELENG_8 will not recognize the 2nd core of my Core Duo (not Core 2 Duo) processor. ?Nobody seems to care as few machines have Core Duo, or few people use this era of Toshiba BIOS, or whatever... and if this is a problem, a boot -v from both releng_7 and releng_8 would be a good starting point. Surely detecting the CPU cores would be an easy thing to get right. Also, it may be a hyperthread CPU "thing" - I recall some changes in the releng_8 timeframe because of security vulnerabilities with classic hyperthreading and you have to do something to enable it again. Adrian
On 31 Dec 2011, at 12:34 PM, Garrett Cooper wrote:> Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and > try booting the new kernel. See if this works.It worked! No hang, power button works. Nice. I hope this experimental option stays in. Thank you everyone for your help. Happy New Years! Dan