Re: Jetson TK1 and kernel 4.8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Peter Robinson [mailto:pbrobinson@xxxxxxxxx]
> Sent: Monday, October 31, 2016 9:35 AM
> To: Timothy Krantz <tkrantz@xxxxxxxxxxxxxxxxxx>
> Cc: arm@xxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [fedora-arm] Re: Jetson TK1 and kernel 4.8
> 
> >> >> > > > > Mine has as of yet failed to boot on any of them.
> >> >> > > >
> >> >> > > > Mine is currently running 4.8.1-1.fc25 without issues, just
> >> >> > > > upgrading it to the latest now to test that too.
> >> >> > >
> >> >> > > Was running 4.8.2-300.fc25.armv7hl+lpae, upgraded to
> >> >> > > 4.8.4-301.fc25 without any issues. Could you post output of
> >> >> > > your
> >> failure?
> >> >> > >
> >> >> > > Paul
> >> >>
> >> >> You might have better luck with a more recent version of U-Boot.
> >> >> I'm running U-Boot 2016.11-rc2 with 4.8.4-301.fc25 on sata.
> >> >>
> >> >>
> >> >
> >> > That made sense to me so I upgraded to the uboot that you are using
> >> > but
> >> same problem.
> >>
> >> Do you have any extra peripherals added like a mPCIe card, camera or
> >> other such things or is it just the base board? What device do you
> >> have the rootfs on? eMMC, SD or SATA?
> >>
> >> I have mine running as a bare device with the OS on the eMMC, I think
> >> Paul might have the OS on a sata SSD. Just trying to work out what if
> >> any differences there are here as there's not much that can be different.
> >>
> >
> > Thanks Peter!
> >
> > Mine is yet another variation.  It is a bare board with the boot partition on an
> SD card and the root filesystem on an SSD.  I left the original eMMC
> untouched until I upgraded the uBoot.
> 
> The u-boot is on SPI nand not the eMMC so I suspect then you didn't even
> touch it.
> 
> > The only thing other than the SDcard and the SSD is the serial console.
> >
> > Just for kicks I tried an LPAE kernel and the first time I booted it got some
> kenel oops that I had not seen before but I was not logging the console output
> so I turned on capture and tried again but have not seen that kernel oops
> since.
> >
> > For some reason my board is not seeing the sata controller (or not getting it
> initialized properly) on 4.7 and 4.8 kernels but does on 4.6.7.
> 
> Is it pulled into the initrd? Do you see the driver with a "lsinitrd | grep ahci"
> 
> > Tim Krantz
> >

Well when booting fails with 4.8.4-lape it finally drops into a Dracut command prompt with no lsinitrd

But all I see in to console logs is about a half dozen of :

tegra-ahci 70027000.sata: couldn't get PHY in node sata: -517

and that is the only reference to ahci

In a good boot on 4.6.7 I do see the driver loaded with lsinitrd | grep ahci.

Tim


_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux