Date: Fri, 13 Nov 2020 21:57:43 +0000 From: Javi Hotmail <volkovdablo@hotmail.com> To: Jason Bacon <bacon4000@gmail.com>, freebsd-ppc@freebsd.org Subject: Re: Question about xserve G5 Message-ID: <DB8PR04MB6860733FB5BDE640CFB048B6ACE60@DB8PR04MB6860.eurprd04.prod.outlook.com> In-Reply-To: <eadf2c5f-f32e-2856-5520-be8c0a06cec7@gmail.com> References: <DB8PR04MB68602F9341DEED4BA6808046AC140@DB8PR04MB6860.eurprd04.prod.outlook.com> <DB8PR04MB6860543600F2C6FDEDF32BD8AC140@DB8PR04MB6860.eurprd04.prod.outlook.com> <88d23ee0-765d-1b82-4318-2c8359018b1a@freebsd.org> <DB8PR04MB6860BC2392B1637417EF8977AC140@DB8PR04MB6860.eurprd04.prod.outlook.com> <DB8PR04MB686092F96B5AEE44D82A1A97AC140@DB8PR04MB6860.eurprd04.prod.outlook.com> <0f4a1ee8-a37f-ea3d-6807-bb2431235a82@gmail.com> <DB8PR04MB6860FB3DE5056A919EFDB71CAC150@DB8PR04MB6860.eurprd04.prod.outlook.com> <de558c8e-f31c-482b-83ec-a8bef521c224@www.fastmail.com> <DB8PR04MB68608DF3EF55DE81641673C3AC150@DB8PR04MB6860.eurprd04.prod.outlook.com> <ee18bb0c-e600-46d9-a8ce-44fd1561b441@www.fastmail.com> <e6611c33-469a-4350-b03b-34f92902163f@www.fastmail.com> <DB8PR04MB6860B75A191D4DB320D71C1DACED0@DB8PR04MB6860.eurprd04.prod.outlook.com> <7647de21-b22d-4204-8dad-070590421eca@www.fastmail.com> <eadf2c5f-f32e-2856-5520-be8c0a06cec7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm trying to boot the XServe with serial console, and I get to the kernel, but immediate after I start getting garbage on the screen (the bauds change to 9600). My issue is that after I reach a point where I have to type something I have no input whatsoever, and I suspect it might be because of this sudden change in bauds. I'm trying to set kernel arguments to fix the bauds to 57600, but I just can't find the correct one. Does anybody know how to do it without recompiling the kernel? Kind Regards, Javi. On 07/11/2020 13:49, Jason Bacon wrote: > On 11/6/20 9:58 AM, Brandon Bergren wrote: >> On Fri, Nov 6, 2020, at 2:59 AM, Javi Hotmail wrote: >> =C2=A0 >>> Internally it was complaining about not being able to read the I2C=C2= =A0 (I >>> assume from the PMU); But anyways it seems to be more or less working >>> now, I'll switch back to FBSD and see how it goes. >>> >> OK, yeah, lack of I2C communication would definitely explain the fans >> suddenly ramping up to maximum, since it's the obvious failsafe to >> use hardware wise when communication gets lost and the thermal >> management system is no longer aware of its temperature. Better to >> err on the side of noise than risk overheating anything. >> > I see I2C errors on my PowerMac G5 as well, but they don't always > correlate with the fans ramping up. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DB8PR04MB6860733FB5BDE640CFB048B6ACE60>