I've attempted to load snv_120 on a Dell M6300 laptop, and
the keyboard doesn't seem to work at all. I tried booting
with -kd and I can set some breakpoints, etc, but once I
let the kernel start, I never see anything from init, etc.
and I can no longer break in via the keyboard.
This machine work
On Sun, Aug 2, 2009 at 12:44 AM, Gordon Ross wrote:
> I've attempted to load snv_120 on a Dell M6300 laptop, and
> the keyboard doesn't seem to work at all. I tried booting
> with -kd and I can set some breakpoints, etc, but once I
> let the kernel start, I never see anything from init, etc.
> and
On Sun, Aug 2, 2009 at 12:52 AM, Martin Bochnig wrote:
> On Sun, Aug 2, 2009 at 12:44 AM, Gordon Ross wrote:
>> I've attempted to load snv_120 on a Dell M6300 laptop, and
>> the keyboard doesn't seem to work at all. I tried booting
>> with -kd and I can set some breakpoints, etc, but once I
>> let
On Sat, Aug 1, 2009 at 3:44 PM, Gordon Ross wrote:
> I've attempted to load snv_120 on a Dell M6300 laptop, and
> the keyboard doesn't seem to work at all. I tried booting
> with -kd and I can set some breakpoints, etc, but once I
> let the kernel start, I never see anything from init, etc.
> and
I had this exact problem with 119 on several machines. There is a fix that
Alan Coopersmith pointed me to. I booted into Failsafe mode and then created
a file in /a/etc/X11 called xorg.conf with the three lines
Section "ServerFlags"
Option "AllowEmptyInput" "False"
EndSection
Then I
will snv_120 be released to the general public [regular Sun download] or is it
reserved as laptop only or something ??
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
I spent a little while rebooting with kmdb and setting breakpoints,
and have narrowed down the failure to this call stack:
main -> startup -> startup_bios_disk -> drive_present
The call to drive_present never returns.
(I guess it's "off in the weeds".)
The drive_present code calls the BIOS, so I
A little more: Out of curiosity, I tried setting "dobiosdev=0" as follows:
Edit the grub line for the kernel to add -kdsv (to the failsafe line).
In kmdb, "dobiosdev/W0". With that, it gets to single-user mode.
So I think this does point at the BIOS-call stuff being broken.
I see (from google) th
I've filed CR 6867906 for this issue.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
>The call to drive_present never returns.
that sounds like edd - i know sysstems where you need to pass "edd=off" to
correctly boot linux.
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e479c8306f898fcdb9b36179071eae6338a17364)
dobiosdev=0 sounds like the solaris e
10 matches
Mail list logo
