Date: Thu, 15 Jan 2009 15:28:37 +0800 From: Ganbold <ganbold@micom.mng.net> To: Harald Servat <redcrash@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 Message-ID: <496EE5A5.3090105@micom.mng.net> In-Reply-To: <d825e0270901141117j54656c5bw1dd323652133a957@mail.gmail.com> References: <d825e0270901131057o12d5e320p6a4182bc9dbf3fe0@mail.gmail.com> <496D41A3.2040306@micom.mng.net> <496D4B60.5050807@micom.mng.net> <d825e0270901141117j54656c5bw1dd323652133a957@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Harald Servat wrote: > However, let me tell you what I've found now (I tried these options in the > following order). > > ** > a) I've started with option 2 (ACPI disabled) because I read somewhere > that FreeBSD did not support Lenovo T400's ACPI. > > The system boots and freezes after showing > (something related with Timecounters) > md0: Preloaded image </boot/mfsroot> 4194304 bytes at <some address> > Trying to mount root from ufs:/dev/md0 > > b) When I chose option Safe mode (3, IIRC) > > Happens the same as a) > > c) I've tried with verbose logging (option 5, I think) > > The initialization dumps a lot of debugging information and after some > time, it brings me the "Choosing region" screen. I didn't get further > because I will not install the system right now (I have to prepare the > backups first ;) ) > > I tried to use ScrollLock + RePag to look for the conflicting line found > in a) or any suspicious message but it didn't work. I also tried with an > holographic shell and the livefs without luck. > > d) I also tried option 1 (default boot) -- just in order to check. > > It also worked. Like c) but without debugging information. > > ** > > So, right now, it seems that the system allows me to begin the > installation of FreeBSD 7.1 amd64 on the T400 but I'm scared due to the lack > of functionality of options 2 and 3. This behavior is not normal, is it? Any > thoughts about this? > I'm using Integrated graphics right now, didn't try option 2,3. I have to find firewire cable to check whether there is something going on when booting with Discrete graphics. You can install FreeBSD with integrated graphics and configure network, ssh etc. and then later try to boot with Discrete graphics. As boot screen stops with |, and as kib@ suggests some time later you can check the machine from the network whether you can login to it via ssh. Also you can try to ping at that time. You can also observe hard disk activity light. If you can ping or ssh then I guess it means boot works and it loads kernel, but something is not allowing to display on the screen. Ganbold -- BACHELOR: A guy who is footloose and fiancee-free.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?496EE5A5.3090105>