1425SC: 2.4 yes, 2.6 no

[Rob Munsch]

Sean Dilda wrote:
> Rob Munsch wrote:
>> Quick question, as i have the issue occurring in the subject whilst 
>> trying to upgrade a 1425SC's kernel:
>>
>> Thanks to a GRUBby combo of fallback and savedefault, it bounces back 
>> into the working 2.4 kernel every time 2.6 fails to boot.  But i am 
>> doing this remotely and don't know WHY it's failing to boot.  I can't 
>> figure out how to craft a google query that asks this, so:  how can i 
>> get dmesg to dump to another file, so when it comes back up in 2.4 i 
>> can look at the failed boot?
>>
> 
> What OS are you running?    RHEL4 has a line in its rc.sysinit like this:
> 
> dmesg -s 131072 > /var/log/dmesg
> 
> You can always put something similar in your rc.local.   Can you tell 
> from the logs if syslog ever gets started under 2.6?  Or does it reboot 
> before then?
> 
> For what its worth, I run CentOS 4 (with a 2.6 kernel) on 1425s.

This is a debian system, and i found something ominous in messages, 
which is where i should have looked of course.  But now i'm wondering 
about the 1425's cd-rom drive.  There's a chance the two different boxes 
i have, tho the same model, have different CD-ROM drives, yah?  I'm not 
liking this, as it only appears when i attempt to boot into 2.6.16.29

-----
Nov 29 08:22:14 wil-ws-2 kernel: hda: packet command error: status=0x51 
{ DriveReady SeekComplete Error }
Nov 29 08:22:14 wil-ws-2 kernel: hda: packet command error: error=0x50
Nov 29 08:22:14 wil-ws-2 kernel: ATAPI device hda:
Nov 29 08:22:14 wil-ws-2 kernel:   Error: Illegal request -- (Sense 
key=0x05)
Nov 29 08:22:14 wil-ws-2 kernel:   Invalid field in command packet -- 
(asc=0x24, ascq=0x00)
Nov 29 08:22:14 wil-ws-2 kernel:   The failed "Start/Stop Unit" packet 
command was:
Nov 29 08:22:14 wil-ws-2 kernel:   "1b 00 00 00 03 00 00 00 00 00 00 00 "
Nov 29 08:22:14 wil-ws-2 kernel: cdrom: open failed.
Nov 29 08:25:57 wil-ws-2 shutdown[19306]: shutting down for system reboot
-----

The last line is where fallback kicks in and the next messages are all 
about it booting into 2.4.  So er.  It's looking like my 2.6 is not 
liking my cdrom drive in this machine?!  I've been googling around the 
parts of this error and see many questions and few answers :D.

-- 
Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com