Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Steven Hartland]

Verbose boot of the working OS version was what I was after, which 
should provide details of what its detecting ;-)


Also a camcontrol identify of the cdrom from the working version may 
also be useful


On 31/03/2015 09:54, Pietro Sammarco wrote:
Currently the cdrom drive and yes it works fine till 10 with the 
legacy ATA stack. Verbose boot doesn't give out any errors or logs 
beside what's shown in the picture I have attached with the first email.


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Pietro Sammarco]

Currently the cdrom drive and yes it works fine till 10 with the legacy 
ATA stack. Verbose boot doesn't give out any errors or logs beside 
what's shown in the picture I have attached with the first email.


Regards,
Pietro Sammarco
On 30/03/2015 21:38, Steven Hartland wrote:

Is there anything connected to the second channel, if so what.

Was this working in a previous version and if so which one and what 
was the verbose boot log from it?


On 30/03/2015 19:07, bsdml wrote:

Hello Kevin,

thanks for your clarification. Unfortunately I wasn't aware that the 
T40 and *4's line used a SATA-PATA convertor and especially that was 
going to clash with the new ATA stack in FreeBSD. Either OpenBSD and 
NetBSD do work out of the box without any hassle, however I'd still 
prefer to use FreeBSD on it as I have been using FreeBSD for about 8 
years now and I am very comfortable with it.


The question at this point is, is there any hope to see this issue 
resolved in the future? Or will I have to give up to the second ATA 
channel in order to use FreeBSD?


Regards,
Pietro Sammarco

On 30/03/2015 06:17, Kevin Oberman wrote:
On Sun, Mar 29, 2015 at 2:27 AM, Wolfgang Zenker 
mailto:wolfg...@lyxys.ka.sub.org>> wrote:


Hi,

* bsdml mailto:pietro.bs...@gmail.com>>
[150329 01:34]:
> since I tried to install FreeBSD 10.1 on my recently purchased 
T40 I got

> stuck at this annoying bootloop that says
> "ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM
status:
> Command timeout". I have also tried latest 11-CURRENT snapshot
and it
> did not make any difference at all, it is affected from the same
exact
> bootloop.
> [..]
> It seems like there might be an issue with the CAM ATA stack 
that is

> clashing with the PATA controller on my T40.

I had the same problem on an ancient T42p. In my case, disabling 
the

second ata channel allowed me to boot.

I added the following line to /boot/device.hints:
hint.ata.1.disabled="1"


This is an annoying side-effect of the brain-dead SATA-PATA 
converter in that generation of ThinkPads. The Intel ICH6 chipset is 
SATA, but, for reasons known ot IBM/Lenovo, the systems used PATA 
drives! So they has a SATA-PATA converter built in that screwed up a 
LOT of things, mostly compromising performance and generating 
assorted log entries. Looks like that also is broken in modern ATA 
support if a drive is not present.


This was always my biggest complaint with this laptop (T42) which I 
used for several years until I retired and returned to so it could 
be excessed legally as it was government property (and, I didn't 
really want it, even if I could have kept it). Not an awful system, 
but this one issue was really annoying to me.

--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com 


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Kevin Oberman]

On Mon, Mar 30, 2015 at 10:49 AM, Garrett Cooper 
wrote:

>
> > On Mar 30, 2015, at 10:38, bsdml  wrote:
> >
> > Hey wolfgang,
> >
> > thanks for getting back to me. Adding hint.ata.1.disabled="1" in
> /boot/device.hints indeed did the trick and allowed me to boot both 10.1
> and 11-CURRENT, however this workaround has temporary solved my problem but
> brings up to another headache. I have planned to get a bay caddy and swap
> the cdrom drive with a 7.200 rpm SATA hdd, but doing this way disabling the
> second SATA channel I will be unable to achieve such a thing.
> >
> > Is there a chance that the bay caddy ATA will work without the need to
> disable the second ATA channel?
>
> Has a bug been filed for this issue?
>
> It's not been fixed and is pretty much unfixable, but it is also only
annoying.

The problem shows up when because the SATA-PATA converter shows the second
drive as present whether it is or not. This leads the driver to try to
probe the drive. The probe of the non-existant fails. (Gee, what a
surprise!)

If you don't have a second PATA drive in hte system, you need to disable
this drive to prevent the probe. If you have a second drive, you only need
to enable it and it works. At least my second drive did on my old T42. I
can only hope the T40 is the same. IF you can get the PATA caddy, try
finding a drive to plug in and see if it works at all. I suspect that it
will.

Be aware that old PATA drives are getting harder to come by. Most are
pretty small, though I did find a 360 GB drive on Amazon.

Good luck!
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Steven Hartland]

Is there anything connected to the second channel, if so what.

Was this working in a previous version and if so which one and what was 
the verbose boot log from it?


On 30/03/2015 19:07, bsdml wrote:

Hello Kevin,

thanks for your clarification. Unfortunately I wasn't aware that the 
T40 and *4's line used a SATA-PATA convertor and especially that was 
going to clash with the new ATA stack in FreeBSD. Either OpenBSD and 
NetBSD do work out of the box without any hassle, however I'd still 
prefer to use FreeBSD on it as I have been using FreeBSD for about 8 
years now and I am very comfortable with it.


The question at this point is, is there any hope to see this issue 
resolved in the future? Or will I have to give up to the second ATA 
channel in order to use FreeBSD?


Regards,
Pietro Sammarco

On 30/03/2015 06:17, Kevin Oberman wrote:
On Sun, Mar 29, 2015 at 2:27 AM, Wolfgang Zenker 
mailto:wolfg...@lyxys.ka.sub.org>> wrote:


Hi,

* bsdml mailto:pietro.bs...@gmail.com>>
[150329 01:34]:
> since I tried to install FreeBSD 10.1 on my recently purchased 
T40 I got

> stuck at this annoying bootloop that says
> "ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM
status:
> Command timeout". I have also tried latest 11-CURRENT snapshot
and it
> did not make any difference at all, it is affected from the same
exact
> bootloop.
> [..]
> It seems like there might be an issue with the CAM ATA stack 
that is

> clashing with the PATA controller on my T40.

I had the same problem on an ancient T42p. In my case, disabling the
second ata channel allowed me to boot.

I added the following line to /boot/device.hints:
hint.ata.1.disabled="1"


This is an annoying side-effect of the brain-dead SATA-PATA converter 
in that generation of ThinkPads. The Intel ICH6 chipset is SATA, but, 
for reasons known ot IBM/Lenovo, the systems used PATA drives! So 
they has a SATA-PATA converter built in that screwed up a LOT of 
things, mostly compromising performance and generating assorted log 
entries. Looks like that also is broken in modern ATA support if a 
drive is not present.


This was always my biggest complaint with this laptop (T42) which I 
used for several years until I retired and returned to so it could be 
excessed legally as it was government property (and, I didn't really 
want it, even if I could have kept it). Not an awful system, but this 
one issue was really annoying to me.

--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com 


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[bsdml]

Hello Kevin,

thanks for your clarification. Unfortunately I wasn't aware that the T40 
and *4's line used a SATA-PATA convertor and especially that was going 
to clash with the new ATA stack in FreeBSD. Either OpenBSD and NetBSD do 
work out of the box without any hassle, however I'd still prefer to use 
FreeBSD on it as I have been using FreeBSD for about 8 years now and I 
am very comfortable with it.


The question at this point is, is there any hope to see this issue 
resolved in the future? Or will I have to give up to the second ATA 
channel in order to use FreeBSD?


Regards,
Pietro Sammarco

On 30/03/2015 06:17, Kevin Oberman wrote:
On Sun, Mar 29, 2015 at 2:27 AM, Wolfgang Zenker 
mailto:wolfg...@lyxys.ka.sub.org>> wrote:


Hi,

* bsdml mailto:pietro.bs...@gmail.com>>
[150329 01:34]:
> since I tried to install FreeBSD 10.1 on my recently purchased T40 I got
> stuck at this annoying bootloop that says
> "ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM
status:
> Command timeout". I have also tried latest 11-CURRENT snapshot
and it
> did not make any difference at all, it is affected from the same
exact
> bootloop.
> [..]
> It seems like there might be an issue with the CAM ATA stack that is
> clashing with the PATA controller on my T40.

I had the same problem on an ancient T42p. In my case, disabling the
second ata channel allowed me to boot.

I added the following line to /boot/device.hints:
hint.ata.1.disabled="1"


This is an annoying side-effect of the brain-dead SATA-PATA converter 
in that generation of ThinkPads. The Intel ICH6 chipset is SATA, but, 
for reasons known ot IBM/Lenovo, the systems used PATA drives! So they 
has a SATA-PATA converter built in that screwed up a LOT of things, 
mostly compromising performance and generating assorted log entries. 
Looks like that also is broken in modern ATA support if a drive is not 
present.


This was always my biggest complaint with this laptop (T42) which I 
used for several years until I retired and returned to so it could be 
excessed legally as it was government property (and, I didn't really 
want it, even if I could have kept it). Not an awful system, but this 
one issue was really annoying to me.

--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com 


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Garrett Cooper]

> On Mar 30, 2015, at 10:38, bsdml  wrote:
> 
> Hey wolfgang,
> 
> thanks for getting back to me. Adding hint.ata.1.disabled="1" in 
> /boot/device.hints indeed did the trick and allowed me to boot both 10.1 and 
> 11-CURRENT, however this workaround has temporary solved my problem but 
> brings up to another headache. I have planned to get a bay caddy and swap the 
> cdrom drive with a 7.200 rpm SATA hdd, but doing this way disabling the 
> second SATA channel I will be unable to achieve such a thing.
> 
> Is there a chance that the bay caddy ATA will work without the need to 
> disable the second ATA channel?

Has a bug been filed for this issue?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[bsdml]

Hey wolfgang,

thanks for getting back to me. Adding hint.ata.1.disabled="1" in 
/boot/device.hints indeed did the trick and allowed me to boot both 10.1 
and 11-CURRENT, however this workaround has temporary solved my problem 
but brings up to another headache. I have planned to get a bay caddy and 
swap the cdrom drive with a 7.200 rpm SATA hdd, but doing this way 
disabling the second SATA channel I will be unable to achieve such a thing.


Is there a chance that the bay caddy ATA will work without the need to 
disable the second ATA channel?


Regards,
Pietro Sammarco

On 29/03/2015 11:27, Wolfgang Zenker wrote:

Hi,

* bsdml  [150329 01:34]:

since I tried to install FreeBSD 10.1 on my recently purchased T40 I got
stuck at this annoying bootloop that says
"ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM status:
Command timeout". I have also tried latest 11-CURRENT snapshot and it
did not make any difference at all, it is affected from the same exact
bootloop.
[..]
It seems like there might be an issue with the CAM ATA stack that is
clashing with the PATA controller on my T40.

I had the same problem on an ancient T42p. In my case, disabling the
second ata channel allowed me to boot.

I added the following line to /boot/device.hints:
hint.ata.1.disabled="1"

Wolfgang


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Kevin Oberman]

On Sun, Mar 29, 2015 at 2:27 AM, Wolfgang Zenker 
wrote:

> Hi,
>
> * bsdml  [150329 01:34]:
> > since I tried to install FreeBSD 10.1 on my recently purchased T40 I got
> > stuck at this annoying bootloop that says
> > "ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM status:
> > Command timeout". I have also tried latest 11-CURRENT snapshot and it
> > did not make any difference at all, it is affected from the same exact
> > bootloop.
> > [..]
> > It seems like there might be an issue with the CAM ATA stack that is
> > clashing with the PATA controller on my T40.
>
> I had the same problem on an ancient T42p. In my case, disabling the
> second ata channel allowed me to boot.
>
> I added the following line to /boot/device.hints:
> hint.ata.1.disabled="1"


This is an annoying side-effect of the brain-dead SATA-PATA converter in
that generation of ThinkPads. The Intel ICH6 chipset is SATA, but, for
reasons known ot IBM/Lenovo, the systems used PATA drives! So they has a
SATA-PATA converter built in that screwed up a LOT of things, mostly
compromising performance and generating assorted log entries. Looks like
that also is broken in modern ATA support if a drive is not present.

This was always my biggest complaint with this laptop (T42) which I used
for several years until I retired and returned to so it could be excessed
legally as it was government property (and, I didn't really want it, even
if I could have kept it). Not an awful system, but this one issue was
really annoying to me.
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[Wolfgang Zenker]

Hi,

* bsdml  [150329 01:34]:
> since I tried to install FreeBSD 10.1 on my recently purchased T40 I got 
> stuck at this annoying bootloop that says
> "ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM status: 
> Command timeout". I have also tried latest 11-CURRENT snapshot and it 
> did not make any difference at all, it is affected from the same exact 
> bootloop.
> [..]
> It seems like there might be an issue with the CAM ATA stack that is 
> clashing with the PATA controller on my T40.

I had the same problem on an ancient T42p. In my case, disabling the
second ata channel allowed me to boot.

I added the following line to /boot/device.hints:
hint.ata.1.disabled="1"

Wolfgang
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

T40 bootloop on CAM status: Command timeout on both 10.1 and -CURRENT

[bsdml]

Hello guys,

since I tried to install FreeBSD 10.1 on my recently purchased T40 I got 
stuck at this annoying bootloop that says
"ATAPY_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 etc etc.. CAM status: 
Command timeout". I have also tried latest 11-CURRENT snapshot and it 
did not make any difference at all, it is affected from the same exact 
bootloop.


I use to boot the kernel and installation image from PXE, however did 
try from usb and didn't make any difference, the bootloop goes on forever.


I did a bunch of researches on Google and somebody suggested to boot 
with hint.achci.0.msi="0" or with hw.achi.force="1" but again it did not 
make any difference.


It seems like there might be an issue with the CAM ATA stack that is 
clashing with the PATA controller on my T40.


Interestingly enough, I did try to remove the cdrom drive and boot the 
installation image with no cd drive installed. However in this case the 
kernel hangs and seat endlessly on the usb controller detection, it does 
not progress or give out any logs past the usb controller recognition.


Unfortunately at the time being it seems like I am stuck with 10 
release, hopefully someone will eventually address this issue so that my 
T40 can see the light again :) .


Here's the link to the picture that showcase the bootloop. 
https://lh4.googleusercontent.com/-XtUvTbUf_pQ/VQy37HOXAwI/HGQ/t8Pjl7oMlls/s512/IMG_20150321_011327.jpg 



Regards,
Pietro Sammarco


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"