Hi Shane, list, I use the term "brick" because I have been unable to recover it in that situation. I exchanged it under warranty for a new unit.
HP has posted a relevant support document here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01658899&lang=en&cc=us&taskId=135&prodSeriesId=3688868&prodTypeId=321957 ...but this did not work for me. My advice for folks is to upgrade to the newest available BIOS before trying tboot. Cheers, -Jon Wang, Shane wrote: > Great to hear that. > > Jon, when you say "Using F.09 will brick the laptop", I am wondering how your > laptop can recover from the brick situation. Or, just remove the battery... > you mentioned in the last email? That will help others. > > Thanks. > Shane > > Jonathan M. McCune wrote: > >> Hello list, >> >> A success story! >> >> I forgot to include intel_iommu=on on the kernel command line (and >> then to use a kernel which supports it). Summary: >> >> Laptop: HP 8530p >> BIOS Revision: F.0E >> tboot revision: changeset: 172:da3ebacc9b6d >> kernel: 2.6.30.6 with CONFIG_DMAR=yes >> grub: >> >> title tboot.hg + Ubuntu 9.04, kernel 2.6.30.6 >> root (hd0,1) >> kernel /tboot.gz logging=vga,memory,serial >> module /vmlinuz-2.6.30.6 root=/dev/sda3 ro intel_iommu=on >> module /initrd.img-2.6.30.6 >> module /GM45_PM45_SINIT_19.BIN >> boot >> >> This works! >> >> HOWEVER: Using BIOS revision F.09 (and I suspect, any earlier version) >> will BRICK THE LAPTOP. I did not try BIOS revision F.0C. >> >> Cheers, >> -Jon >> > > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
