Nitdroid Problem - Multiboot

Today i installed nitdroid N11 acording to the wiki instructions. I had some doubts but i believe i did it right. When all steps were completed i turned the N900 of and when i turned it on i was able to use the android. Then i wanted to do the upgrade to nitdroid N12 so i reboot (from nitdroid) and booted with maemo. it asked for the PIN code but then it didn't started... it stayed for over 5 minutes trying to start (those 5 dots blinking) then i pressed the on/off button to turn it off... The results are: multiboot not working (only maemo boot) and sometimes the same "error" happens and after the PIN code it doesn't start. Can anyone help me? have i bricked my N900? Help please
Solved!
Go to Solution.

i haven't used nitdroid for a while now but with multiboot you used to have to have the keypad open when powering up.
its possible that the deamon (background process) that asks for a pin number is having issues with multiboot but i can't say for sure
it might help if you remove the battery, hold the power button down for 5 seconds then replace the battery and restart

Similar Messages

Multiboot USB Problem

Hi
What I'm doing wrong? drive won't boot
USB disk is bootable
All files are available on the drive
when using original bcd file drive boots without problems
I have copied setting with bcdedit /copy option
WIM and Boot files are 32bit
Here is my BCD settings
Windows Boot Manager
identifier              {bootmgr}
description             Boot Disk
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {739f13a1-ce6c-11e4-8b42-001a92c912db}
toolsdisplayorder       {memdiag}
timeout                 30
Windows Boot Loader
identifier              {default}
device                  ramdisk=[boot]\Sources\BD.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Boot Disk
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\Sources\BD.wim,{default}
systemroot              \windows
custom:250000c2         1
detecthal               Yes
winpe                   Yes
ems                     No
Windows Boot Loader
identifier              {739f13a1-ce6c-11e4-8b42-001a92c912db}
device                  ramdisk=[boot]\Sources\NBRT.wim,{739f13a1-ce6c-11e4-8b42-001a92c912db}
path                    \windows\system32\boot\winload.exe
description             Norton Bootable Recovery Tool
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\Sources\NBRT.wim,{739f13a1-ce6c-11e4-8b42-001a92c912db}
systemroot              \windows
custom:250000c2         1
detecthal               Yes
winpe                   Yes
ems                     No

Hi,
Was your issue resolved?
If yes, we will archive this thread temporarily.
If no, please reply and tell us the current situation.
If you have any other question, feel free to contact us. We will try our best to help you.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Problem booting Solaris 10 on ProLiant server after installation.

Hi all!
I have a brand new HP ProLiant DL360 G5 server. It contains 6 internal
hard drives. RAID 5 is configured on these drives using built-in HP
Smart Array P400i controller. I've just installed Solaris 10 8/07 on this
server. Solaris requires a driver for P400i controller. I'm using Driver
Update CD created from HP provided ISO image. Solaris 10 is
officially supported OS for DL360 G5 server.
Installation proceeds as expected:
1) At the begining of Solaris installation, Driver Update is used to
load HP driver for raid controller. During installation, disk is
recognized as c1d0t0 (the only disk in system); one partition is
created on this disk.
2) Disk is devided to 6 slices:
c1d0t0s0 - swap, 4GB
c1d0t0s1 - /, cca 32GB
c1d0t0s[3,4,5,6] - /zones/[a,b,c,d] - each cca 160GB
3) At the end of installation, CPQary3 driver is installed to target
system without any errors reported. No errors are reported during
installation at all.
After reboot, GRUB is started. It shows boot menu containing two
options:
- Solaris 'normal' boot
- failsafe boot
PROBLEM: Selecting 'normal' boot leads to immediate system restart.
According to documentation, this case occurs when PCQary3
driver is not installed.
I'm able to boot using 'failsafe' option in grub. After entering single
user, I load PCQary3 driver to runtime using 'install-du' command.
I'm also able to find instaled Solaris using 'install-recovery' and mount
its root volume to /a directory. Necessary driver IS installed inside
/a/kernel/drv/ directory. Options 'bootpath' in /a/boot/solaris/bootenv.rc
file is set up correctly pointing to device associated with /dev/dsk/c1d0t0s1
device. Also GRUB is able to recognize UFS filesystem for boot partition.
I've already tried (without success):
1) Use RAID 1+0 instead of RAID5
2) Create only 3,5GB partition instead of 700GB large one.
3) Place / on c1d0t0s0 instead of c1d0t0s1.
4) Re-create boot archive using 'bootadm update-archive -R /a'
So, everything seems to be installed correctly, but system cannot boot.
Do you have any ideas how to fix this problem?
Jozef

Sounds like an issue I just had with a brand new X4150, installation and failsafe worked fine, but normal booting led to immediate reboot of the server. This was due to an incompatibility of solaris and intel's newest generation xeon chips.
You can still boot 'normal' solaris in 32-bit mode:
hit 'e' at the grub menu, 'e' again to edit the 'normal' boot entry and add 'kernel/unix' after multiboot. This should boot up solaris in 32-bit mode. From there, download and install the latest patch set (125370-06 and 127112-05 are fixing this issue). After that you should be fine.
Bjoern

X86 installation problems.

Hardware: Asus motherboard MP NPV VM with Nvidea graphics, Amd x2 3600 processor
Installed Version Solaris 10 11/06 update
Problems: 1) Network card was not detected. So Internet can't be configured. 2) Display resolution problems with some monitors - some had maximum resolution that can't be changed at 480x600 in some the resolution was a little better but now on a samptron monitor the resolution is 1024x800. 3) The cursor of the mouse becomes invisible when logged out and logged back in or when restarted (instead of shut down) 4) Star office instalation started displaying errors - the installation progressed well upto 50% stage, but after that over a hundred files could not be installed
The following is the output of the prtconf -v :
System Configuration: Sun Microsystems i86pc
Memory size: 479 Megabytes
System Peripherals (Software Nodes):
i86pc
System properties:
name='acpi-status' type=int items=1
value=00000013
name='relative-addressing' type=int items=1
value=00000001
name='MMU_PAGEOFFSET' type=int items=1
value=00000fff
name='MMU_PAGESIZE' type=int items=1
value=00001000
name='PAGESIZE' type=int items=1
value=00001000
name='biosdev-0x80' type=byte items=588
value=01.eb.04.4d.33.2e.30.fa.fc.be.00.7c.bf.00.06.8c.c8.8e.d0.89.f4.8e.c0.8e.d8.51.b9.00.01.f3.a5.59.e9.00.8a.fb.b4.02.cd.16.24.03.3c.03.75.05.c6.06.61.07.01.bb.be.07.b9.04.00.80.3f.80.74.0e.83.c3.10.e2.f6.bd.75.07.b9.13.00.e9.e6.00.b4.00.cd.13.53.b4.41.bb.aa.55.b9.00.00.cd.13.72.3f.81.fb.55.aa.75.39.f7.c1.01.00.74.33.bd.a4.07.b9.03.00.e8.c8.00.5b.53.b9.05.00.66.6a.00.66.ff.77.08.66.ff.36.5c.07.6a.01.6a.10.b4.42.89.e6.cd.13.9f.83.c4.10.9e.73.7b.b4.00.cd.13.e2.dd.eb.6b.bd.a7.07.b9.03.00.e8.95.00.5b.53.8a.16.60.07.b4.08.cd.13.73.08.bd.62.07.b9.13.00.eb.79.88.c8.24.3f.a2.59.07.fe.c6.f6.e6.a3.5a.07.8b.47.08.8b.57.0a.f7.36.5a.07.89.c3.89.d0.f6.36.59.07.fe.c4.30.c9.88.fd.c1.e9.02.80.e1.c0.08.e1.88.dd.88.c6.8a.16.60.07.c4.1e.5c.07.be.05.00.b8.01.02.cd.13.73.12.b4.00.cd.13.4e.83.fe.00.75.ef.bd.88.07.b9.0e.00.eb.23.bb.00.7c.81.bf.fe.01.55.aa.74.08.bd.96.07.b9.0b.00.eb.10.8a.16.60.07.5e.66.ff.16.5c.07.bd.a1.07.b9.03.00.bb.4f.00.e8.0c.00.cd.18.80.3e.61.07.00.74.18.bb.1f.00.60.b8.01.13.ba.00.17.cd.10.b0.07.b9.01.00.cd.10.b4.00.cd.16.61.c3.00.00.00.00.7c.00.00.80.00.43.61.6e.27.74.20.72.65.61.64.20.67.65.6f.6d.65.74.72.79.4e.6f.20.61.63.74.69.76.65.20.70.61.72.74.69.74.69.6f.6e.43.61.6e.27.74.20.72.65.61.64.20.50.42.52.42.61.64.20.50.42.52.20.73.69.67.21.21.21.4c.42.41.43.48.53.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.80.00.01.01.bf.fe.ff.ff.c1.3e.00.00.00.4c.a1.12.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.55.aa.01.1e.00.00.00.ff.3f.00.00.10.00.00.00.3f.00.00.00.b0.9e.a1.12.00.00.00.00.00.02.b0.96.00.f0.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
name='kbd-type' type=string items=1
value='US-English'
name='ata-dma-enabled' type=string items=1
value='1'
name='atapi-cd-dma-enabled' type=string items=1
value='0'
name='ttyb-rts-dtr-off' type=string items=1
value='false'
name='ttyb-ignore-cd' type=string items=1
value='true'
name='ttya-rts-dtr-off' type=string items=1
value='false'
name='ttya-ignore-cd' type=string items=1
value='true'
name='ttyb-mode' type=string items=1
value='9600,8,n,1,-'
name='ttya-mode' type=string items=1
value='9600,8,n,1,-'
name='lba-access-ok' type=string items=1
value='1'
name='prealloc-chunk-size' type=string items=1
value='0x2000'
name='bootpath' type=string items=1
value='/pci@0,0/pci-ide@e/ide@0/cmdk@0,0:a'
name='console' type=string items=1
value='text'
name='bootprog' type=string items=1
value='/platform/i86pc/multiboot'
name='boot-args' type=unknown items=1
value=00
name='ramdisk_start' type=int items=2
value=01034000.00000000
name='ramdisk_end' type=int items=2
value=055f1000.00000000
name='mfg-name' type=string items=1
value='i86pc'
name='impl-arch-name' type=string items=1
value='i86pc'
name='whoami' type=string items=1
value='/platform/i86pc/kernel/amd64/unix'
name='mmu-modlist' type=string items=1
value='mmu64'
Hardware properties:
name='bios-boot-device' type=string items=1
value='80'
name='stdout' type=int items=1
value=00000000
scsi_vhci, instance #0
System properties:
name='class' type=string items=1
value='root'
name='load-balance' type=string items=1
value='round-robin'
name='auto-failback' type=string items=1
value='enable'
Driver properties:
name='pm-want-child-notification?' type=boolean dev=none
name='initiator-interconnect-type' type=string items=1 dev=(174,0)
value='SPI'
name='scsi-selection-timeout' type=int items=1 dev=(174,0)
value=000000fa
name='scsi-options' type=int items=1 dev=(174,0)
value=00107ff8
name='scsi-watchdog-tick' type=int items=1 dev=(174,0)
value=0000000a
name='scsi-tag-age-limit' type=int items=1 dev=(174,0)
value=00000002
name='scsi-reset-delay' type=int items=1 dev=(174,0)
value=00000bb8
Device Minor Nodes:
dev=(174,0)
dev_path=/scsi_vhci:devctl
spectype=chr type=minor
isa, instance #0
Hardware properties:
name='bus-type' type=string items=1
value='isa'
name='device_type' type=string items=1
value='isa'
fdc, instance #0
Driver properties:
name='chip' type=int items=1 dev=none
value=00082077
Hardware properties:
name='dma-channels' type=int items=1
value=00000002
name='interrupts' type=int items=1
value=00000006
name='reg' type=int items=6
value=00000001.000003f0.00000006.00000001.000003f7.00000001
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.FDC0'
name='model' type=string items=1
value='PC standard floppy disk controller'
name='compatible' type=string items=1
value='PNP0700'
Register Specifications:
Bus Type=0x1, Address=0x3f0, Size=0x6
Bus Type=0x1, Address=0x3f7, Size=0x1
Interrupt Specifications:
Interrupt Priority=0x5 (ipl 5), vector=0x6 (6)
fd, instance #0
System properties:
name='mode_3D' type=int items=1
value=00000000
name='unit' type=int items=1
value=00000000
Driver properties:
name='ddi-kernel-ioctl' type=boolean dev=none
Device Minor Nodes:
dev=(36,0)
dev_path=/isa/fdc@1,3f0/fd@0,0:a
spectype=blk type=minor
dev_link=/dev/fd0a
dev_path=/isa/fdc@1,3f0/fd@0,0:a,raw
spectype=chr type=minor
dev_link=/dev/rfd0a
dev=(36,1)
dev_path=/isa/fdc@1,3f0/fd@0,0:b
spectype=blk type=minor
dev_link=/dev/fd0b
dev_path=/isa/fdc@1,3f0/fd@0,0:b,raw
spectype=chr type=minor
dev_link=/dev/rfd0b
dev=(36,2)
dev_path=/isa/fdc@1,3f0/fd@0,0:c
spectype=blk type=minor
dev_link=/dev/diskette
dev_link=/dev/diskette0
dev_link=/dev/fd0
dev_link=/dev/fd0c
dev_path=/isa/fdc@1,3f0/fd@0,0:c,raw
spectype=chr type=minor
dev_link=/dev/rdiskette
dev_link=/dev/rdiskette0
dev_link=/dev/rfd0
dev_link=/dev/rfd0c
asy, instance #0 (driver not attached)
System software properties:
name='interrupt-priorities' type=int items=1
value=0000000c
Hardware properties:
name='interrupts' type=int items=1
value=00000004
name='reg' type=int items=3
value=00000001.000003f8.00000008
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.UAR1'
name='model' type=string items=1
value='16550A-compatible COM port'
name='compatible' type=string items=1
value='PNP0501'
Register Specifications:
Bus Type=0x1, Address=0x3f8, Size=0x8
Interrupt Specifications:
Interrupt Priority=0xc (ipl 12), vector=0x4 (4)
asy, instance #1 (driver not attached)
System software properties:
name='interrupt-priorities' type=int items=1
value=0000000c
Hardware properties:
name='interrupts' type=int items=1
value=00000003
name='reg' type=int items=3
value=00000001.000002f8.00000008
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.UAR2'
name='model' type=string items=1
value='16550A-compatible COM port'
name='compatible' type=string items=1
value='PNP0501'
Register Specifications:
Bus Type=0x1, Address=0x2f8, Size=0x8
Interrupt Specifications:
Interrupt Priority=0xc (ipl 12), vector=0x3 (3)
lp (driver not attached)
Hardware properties:
name='interrupts' type=int items=1
value=00000007
name='reg' type=int items=3
value=00000001.00000378.00000008
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.LPT1'
name='model' type=string items=1
value='Standard LPT printer port'
name='compatible' type=string items=1
value='PNP0400'
i8042, instance #0
Hardware properties:
name='unit-address' type=string items=1
value='1,60'
name='interrupts' type=int items=2
value=00000001.0000000c
name='reg' type=int items=6
value=00000001.00000060.00000001.00000001.00000064.00000001
Register Specifications:
Bus Type=0x1, Address=0x60, Size=0x1
Bus Type=0x1, Address=0x64, Size=0x1
Interrupt Specifications:
Interrupt Priority=0x5 (ipl 5), vector=0x1 (1)
Interrupt Priority=0x5 (ipl 5), vector=0xc (12)
mouse, instance #0
Driver properties:
name='ddi-no-autodetach' type=int items=1 dev=none
value=00000001
Hardware properties:
name='device-type' type=string items=1
value='mouse'
name='reg' type=int items=1
value=00000001
name='interrupts' type=int items=1
value=0000000c
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.PS2M'
name='model' type=string items=1
value='PS/2 Port for PS/2-style Mice'
name='compatible' type=string items=1
value='pnpPNP,f03'
Device Minor Nodes:
dev=(116,0)
dev_path=/isa/i8042@1,60/mouse@1:l
spectype=chr type=minor
dev_link=/dev/kdmouse
dev=(116,1)
dev_path=/isa/i8042@1,60/mouse@1:internal_mouse
spectype=chr type=internal
Device Minor Layered Under:
mod=consms accesstype=chr
dev_path=/pseudo/consms@0
keyboard, instance #0
Driver properties:
name='ddi-no-autodetach' type=int items=1 dev=none
value=00000001
Hardware properties:
name='device-type' type=string items=1
value='keyboard'
name='interrupts' type=int items=2
value=00000001.0000000c
name='reg' type=int items=1
value=00000000
name='_CID' type=string items=1
value='PNP030B'
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.PS2K'
name='model' type=string items=1
value='IBM Enhanced (101/102-key, PS/2 mouse support)'
name='compatible' type=string items=1
value='pnpPNP,303'
Device Minor Nodes:
dev=(101,0)
dev_path=/isa/i8042@1,60/keyboard@0:kb8042
spectype=chr type=minor
Device Minor Layered Under:
mod=conskbd accesstype=chr
dev_path=/pseudo/conskbd@0
none (driver not attached)
Hardware properties:
name='interrupts' type=int items=1
value=0000000a
name='reg' type=int items=3
value=00000001.00000330.00000002
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.MIDI'
name='model' type=string items=1
value='Audio MIDI interface (MPU401 UART)'
name='compatible' type=string items=1
value='PNPB006'
joyst (driver not attached)
Hardware properties:
name='reg' type=int items=3
value=00000001.00000201.00000001
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.GAME'
name='model' type=string items=1
value='Game port (Joy stick)'
name='compatible' type=string items=1
value='PNPB02F'
motherboard (driver not attached)
Hardware properties:
name='reg' type=int items=45
value=00000000.000f0000.00004000.00000000.000f4000.00004000.00000000.000f8000.00004000.00000000.000fc000.00004000.00000000.1def0000.00010000.00000000.ffff0000.00010000.00000000.00000000.000a0000.00000000.00100000.1ddf0000.00000000.1df00000.02000000.00000000.fec00000.00001000.00000000.fee00000.00100000.00000000.fefff000.00001000.00000000.fff80000.00001000.00000000.fff90000.00030000.00000000.fffed000.00003000
name='acpi-namespace' type=string items=1
value='\_SB_.MEM_'
name='model' type=string items=1
value='Motherboard'
name='compatible' type=string items=1
value='PNP0C01'
pci, instance #0
Driver properties:
name='device_type' type=string items=1 dev=none
value='pciex'
Hardware properties:
name='ecfga-base-address' type=int64 items=1
value=00000000f0000000
name='available' type=int items=145
value=81000000.00000000.00000000.00000000.00000170.81000000.00000000.00000178.00000000.00000078.81000000.00000000.000001f8.00000000.0000017e.81000000.00000000.00000377.00000000.0000007f.81000000.00000000.000003f7.00000000.00000569.81000000.00000000.00000968.00000000.00000008.81000000.00000000.00000978.00000000.00000068.81000000.00000000.000009e8.00000000.00000008.81000000.00000000.000009f8.00000000.0000016a.81000000.00000000.00000b63.00000000.0000000f.81000000.00000000.00000b73.00000000.0000006f.81000000.00000000.00000be3.00000000.0000000f.81000000.00000000.00000bf3.00000000.0000400d.81000000.00000000.00004c80.00000000.00003380.81000000.00000000.0000c000.00000000.00000800.81000000.00000000.0000c808.00000000.000003f8.81000000.00000000.0000cc10.00000000.000013f0.81000000.00000000.0000e010.00000000.000013f0.81000000.00000000.0000f410.00000000.00000bf0.82000000.00000000.1df00000.00000000.00100000.82000000.00000000.20000000.00000000.c0000000.82000000.00000000.f4000000.00000000.07000000.82000000.00000000.fd000000.00000000.00800000.82000000.00000000.fd900000.00000000.00200000.82000000.00000000.fdd00000.00000000.00100000.82000000.00000000.fdf00000.00000000.00124000.82000000.00000000.fe028000.00000000.00003000.82000000.00000000.fe02e100.00000000.00000f00.82000000.00000000.fe030000.00000000.00bd0000
name='bus-range' type=int items=2
value=00000000.00000004
name='compatible' type=string items=1
value='pciex_root_complex'
name='device_type' type=string items=1
value='pciex'
name='reg' type=int items=3
value=00000000.00000000.00000000
name='#size-cells' type=int items=1
value=00000002
name='#address-cells' type=int items=1
value=00000003
Register Specifications:
Bus Type=0x0, Address=0x0, Size=0x0
Device Minor Nodes:
dev=(183,255)
dev_path=/pci@0,0:devctl
spectype=chr type=minor
dev=(183,253)
dev_path=/pci@0,0:reg
spectype=chr type=minor
dev=(183,252)
dev_path=/pci@0,0:intr
spectype=chr type=minor
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000000.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,2f0.1043.81c0.a2' + 'pci10de,2f0.1043.81c0' + 'pci1043,81c0' + 'pci10de,2f0.a2' + 'pci10de,2f0' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='fast-back-to-back' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=000002f0
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000100.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,2fa.1043.81c0.a2' + 'pci10de,2fa.1043.81c0' + 'pci1043,81c0' + 'pci10de,2fa.a2' + 'pci10de,2fa' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0,1'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=000002fa
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000200.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,2fe.1043.81c0.a2' + 'pci10de,2fe.1043.81c0' + 'pci1043,81c0' + 'pci10de,2fe.a2' + 'pci10de,2fe' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0,2'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=000002fe
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000300.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,2f8.1043.81c0.a2' + 'pci10de,2f8.1043.81c0' + 'pci1043,81c0' + 'pci10de,2f8.a2' + 'pci10de,2f8' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='fast-back-to-back' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0,3'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=000002f8
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000400.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,2f9.1043.81c0.a2' + 'pci10de,2f9.1043.81c0' + 'pci1043,81c0' + 'pci10de,2f9.a2' + 'pci10de,2f9' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='fast-back-to-back' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0,4'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=000002f9
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000500.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,2ff.1043.81c0.a2' + 'pci10de,2ff.1043.81c0' + 'pci1043,81c0' + 'pci10de,2ff.a2' + 'pci10de,2ff' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='fast-back-to-back' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0,5'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=000002ff
pci1043,81c0 (driver not attached)
Hardware properties:
name='reg' type=int items=5
value=00000600.00000000.00000000.00000000.00000000
name='compatible' type=string items=7
value='pci10de,27f.1043.81c0.a2' + 'pci10de,27f.1043.81c0' + 'pci1043,81c0' + 'pci10de,27f.a2' + 'pci10de,27f' + 'pciclass,050000' + 'pciclass,0500'
name='model' type=string items=1
value='Ram'
name='power-consumption' type=int items=2
value=00000001.00000001
name='66mhz-capable' type=boolean
name='devsel-speed' type=int items=1
value=00000000
name='max-latency' type=int items=1
value=00000000
name='min-grant' type=int items=1
value=00000000
name='subsystem-vendor-id' type=int items=1
value=00001043
name='subsystem-id' type=int items=1
value=000081c0
name='unit-address' type=string items=1
value='0,6'
name='class-code' type=int items=1
value=00050000
name='revision-id' type=int items=1
value=000000a2
name='vendor-id' type=int items=1
value=000010de
name='device-id' type=int items=1
value=0000027f
pci1043,81c0 (driver not attached)
Hardware properties:

hi Sivasubramanian,
as i'm on a vacation in San Francisco (i'm writing this on my Cingular 8525 Windows Pocket PC 5) I won't be able to take a look at the
report...(my email is jags_fl at yahoo dot com) but after u ran installation check tool did u look at the results? check for those 'Y' & 'N' as showed on following page:
http://www.sun.com/bigadmin/hcl/hcts/install_check.html
u would be able to see urself if any hardware is not compatible (at the end of installation check tool)...
- Jags Desai

X100e win xp pro usb installation problem

Hello to all, i am new here and sorry for not not introducing myself properly bu this is urgent situation.
Few days ago i bought Lenovo x100e Netbook
Product ID: 35086AG
Athlon MV40(1.6GHz), 1GB RAM, 160GB 5400rpm HD, 11.6in 1366x768 LCD, ATI Radeon HD2200, 802.11bgn wireless, WWAN upgradeable, Bluetooth, 1Gb Ethernet, UltraNav, 3c Li-Ion, WinXP Home 32
here is link from lenovo driver download site for this netbook:
http://www-307.ibm.com/pc/support/site.wss/quickPath.do?quickPathEntry=35086AG
Netbook came with preinstalled Win. XP Home edition and i was going to install Win. XP Professional.
So i created bootable USB stick Win. XP Pro. installation (cause this netbook dont have internal cd drive) and booted on startup and started installation.
Installation was going smooth -> i choosed C partition, formated it and after formatting next message shows up:
"The following value in the .SIF file used by Setup is
corrupted or missing:
Value 0 on the line in section [SourceDiskFiles]
with key "SSA.exe."
Setup cannot continue. To quit Setup, press F3."
So as you can see...i can't go on with installation and problem is the disk is already formatted and i have nothing on it, no OS no nothing.
Please help cause i need laptop soon.
Solved!
Go to Solution.

I solved problem,
As i could not find vanilla, i found standard Win. XP Pro. with SP3, and using nLite added ATI AMD RAID AHCI driver to it and using multiboot 10 put that on USB stick. It booted with no problems and installed
Thank you for pointing me in right direction.

Problem booting a Solaris 10 x86 after Jumpstart Installation

Hi,
I have a strange problem. I have a working x86 machine with Solaris 10 installed. I have made a flash image of it's hard disk, and I have store thar flar on another machine. I have another Solaris 10 with Jumpstart.
I boot other x86 machine through PXE. The Jumpstart machine gives it a valid IP, and the process of sending the flash image begins. The process finish, and the client machine reboots. And here is the strange problem:
When starting, the Grub men� appears, and shows the two options configured: first, start Solaris in normal mode, and second, failsafe.
If I choose normal start, the screen goes black and the machine restart as if you rebooted it. I can only start in failsafe mode.
Here are the config files in Jumpstart for that machine:
Profile:
install_type flash_install
archive_location nfs 10.95.8.7:/export/backup/platform/alba-ucm/ALBA-UCM-HostID_2b72c461_4x80GbMirror-Prepared_09042008.flar
partitioning explicit
filesys c0t0d0s0 1:2650 /
filesys c0t0d0s1 2651:1600 /var
filesys c0t0d0s3 4251:400 swap
filesys c0t0d0s4 4651:1000 /opt/app
filesys c0t0d0s5 5651:3143 /repositoryCC
filesys c0t0d0s6 8794:100 /tmp
filesys c0t0d0s7 8894:26
filesys c0t2d0s0 1:8093 /datos
filesys c0t2d0s1 8094:800 /DBoracle
filesys c0t2d0s7 8894:26
After Script:
touch /a/etc/notrouter
touch /a/noautoshutdown
sync
echo "Changing and syncing bootenv.rc"
# clear the boot-args property
echo "setprop boot-args ''" >> /a/boot/solaris/bootenv.rc
# set the bootpath property to boot from the hard disk
STRING=`df | grep '^/a '� | sed 's/).*//' | sed 's/^.* (//'`
STRING=`ls -l ${STRING}`
MYROOT=`echo $STRING | sed 's/.*..\/..\/devices//'`
echo "setprop bootpath ${MYROOT}" >> /a/boot/solaris/bootenv.rc
# disable kdmconfig from running after the first reboot
sysidconfig -b /a -r /usr/openwin/bin/kdmconfig
sync
And here is the menu.lst for Grub:
title Solaris 10
root (hd0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
title Solaris Failsafe
kernel /boot/multiboot kernel/unix -s
module /boot/x86.miniroot-safe
Please, any idea about what may be hapening?

Thanks for your answers.
Yes, both machines have the same hardware exactly. Finally, I could find where the problem was.
The file bootenv.rc, for some reason that I don't know, was corrupted: In it there was a correct line with bootpath variable correctly defined, but, at the end of the file, there was another line setting the bootpath variable to a long and incoherent string of chars. Booting in failsafe, mounting the system in /a, and removing that stupid line from the bootenv.rc, solved the problem.

Weird problems with recovery partition

Hi. I just got a new X1 Carbon a few days ago. When trying to install Ubuntu, I messed up the bootmgr. At that point I still had the option F11 for recovery on startup, but choosing it did not give any results and after a restart, the option was gone. When researching the problem, I found this thread:
http://forums.lenovo.com/t5/ThinkVantage-Technologies/Need-help-with-recovery-partition-create-recov...
Since my recovery partition Q was untouched, the steps described in the thread allowed me to restore partitions S and C. So far so good, but now the problems start.
First, the letters of the partitions get messed up after every reboot. I assign Windows7_OS the letter C, SYSTEM_DRV gets S, and Lenovo_Recovery gets Q. Diskpart then lists the drives with correct letters. But after a reboot, they're back to D,C,E, respectively.
Then, when I boot the Windows recovery disk from a usb stick, it correctly recognizes that Windows is installed on drive D. It suggests that there are startup problems, which I tell it to fix. After the next reboot, it does not warn me about startup problems. When I then go to command prompt and enter
bootrec.exe /fixmbr
bootrec.exe /fixboot
then the Windows recovery disk commits suicide. It seems to attempt to fix its own bootmgr. At the moment, both usb stick and hard disk run with grub (Windows recovery on a multiboot installed by YUMI). After I run the commands above, the hard disk still runs with grub, but the usb stick now has bootmgr and fails to boot. I have tried this several times, each time recreating the Windows recovery disk with YUMI, and every time the same result.
F11 option is of course still gone. At this point I'm out of my wits. Any suggestions are welcome.
Solved!
Go to Solution.

In the end I formatted and made a clean install. F11 Option is gone. Recovery partition is still untouched, but I don't think it will be used again. Followed this advice to install a fresh Windows 7 using a usb stick:
http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164
Since I did not have access to Windows with administrator rights, I had to use Ubuntu to create the bootable Windows stick:
http://cloud101.eu/blog/2012/03/24/create-a-windows-7-live-disk-from-ubuntu-linux/
The WiFi driver was not included in Windows, so I had to download that in another system, and install manually. From there I could then go online in Windows to download the remaining drivers from Lenovo (after the clean install there's a long list of unrecognized devices).
Since the laptop comes with 4 primary partitions preinstalled I had to merge the SYSTEM_DRV and the Windows7_OS partition in order to create an additional partition for Ubuntu. Then I installed Ubuntu and took control of the startup behavior using EasyBCD.

[solved] Booting a "Multiboot" OS only works with high amounts of mem

edit: ok, I hate when it happens, but I've just found the solution: raising the memory reserved for the virtual machine. It's funny, however, that such simple kernel won't boot with less than 128MB of RAM.
I'm not sure if this is the right place to post this question, but as it's at least indirectly related to programming, I'll post it here.
Recently I've read Tenenbaum's book about Minix and now I'm feeling like hacking a simple OS if only for saying "I can do it". The problem is I got stuck right at the first step: booting. I wasn't willing to implement a bootloader so I decided to use Grub and implement a Multiboot compatible kernel.
Running 'info multiboot' you can see a example showing how to implement a "multiboot" kernel. I used exactly the same code and compiled it with:
gcc -nostartfiles -nodefaultlibs -o kernel boot.S kernel.c
The code compiles with two warnings about redefinitions of printf, but it gives no errors. The 'kernel' file is less than 3KB big and running 'objdump -d kernel' seems to be fine.
Satisfied with it, I've tried to create an ISO image so I could test it in a virtual machine (VirtualBox). I followed the instructions from Grub manual of how to install it in a CD (create a iso/boot/grub/ folder, put stage2_eltorito there, etc). I also created a menu.lst like this:
default 0
timeout 30
fallback 1
title Test
root (cd)
kernel /boot/kernel
and created the ISO image with: 'mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 -boot-info-table -o grub.iso iso' .
I've tried to run it in a virtual machine and it boots, but when I press enter to run 'Test', which should run the kernel from the 'multiboot' example, grub gives me an error:
Booting 'Test'
root (cd)
Filesystem type is iso9660, using whole disk.
kernel /boot/kernel
[Multiboot-elf, <0x8048000:0x803:0x0>
Error 28: Selected item cannot fit into memory.
Press any key to continue...
And then it fallsback to the menu. (The menu shows [639k lower / 64448k upper memory])
Last edited by andre.ramaciotti (2009-10-12 19:54:04)

The linker is compiling your binary to the default location of 0x8000000. This is fine for Linux to load as an application (even with less than 128MB memory, Linux can use the MMU on the CPU to map anything to 0x8000000). However with ring0 code you are dealing with real physical memory locations. You would need either a linker script (which you can look up, also see: http://wiki.osdev.org/Linker_Scripts) or to specify the options on the command line with
ld -Ttext 0x100000 etc.
0x100000 is at 1MB, so that leaves BIOS memory unaffected. For memory management past that you should read a memory map, which is beyond the scope of this.
Edit: Fix formatting issues.
Last edited by sdkmvx (2009-10-12 19:41:52)

Problematic transition to systemd on a multiboot pc

Hallo, I'm a bit lazy so I didn't modify yet my system to use systemd
After consolekit has been removed I couldn't start my system so I had to modify my grub adding init=/usr/lib/systemd/systemd to the kernel parameters of grub according to wiki.
The problem is that I never installed grub on archlinux because I have a multiboot system and I can use the grub of ubuntu (version 1.99 last official update on 12.04) that automatically notice all the system installed.
I added the string manually but there is any way to tell to grub to add this parameter? I already know that i can use the section 40_custom to add other system but the question is what happens if I add a system that is automatically taken by os_prober?
Thank you very much, sorry for my poor english

O.K. the solution seems to be to start slim as a daemon which it is not by default.
Issue
sudo vim /usr/lib/systemd/system/slim.service
or open the file with any other text editor.
Then change line 6 from
ExecStart=/usr/bin/slim -nodaemon
to
ExecStart=/usr/bin/slim
Save. Exit. And reboot. Everything should work now. At least it does for me.
Last edited by ichi-no-eda (2012-08-05 20:42:18)

Multiboot USB image?

Hi,
on my desktop PC I've arch x86_64 installed but my netbook only allows the installation of a i686 system.
I always like to have an usb drive with an arch linux image on it so I can e.g. make a fsck if something is going wrong or just to use it for installation.
The problem is that there isn't an image available that is able to install both a 64 and a 32 bit system.
Is there a way or are there plans to make a multiboot image available so that one only needs one single usb drive?
Thanks
barghest
/edit: maybe this was better be placed in "installation"...sorry.
Last edited by Barghest (2010-01-30 14:59:10)

Tpowa makes some great "unofficial" installation images. His one includes both 32 and 64bit on one image.
http://bbs.archlinux.org/viewtopic.php?id=77017

NITDroid with BackupMenu

while i have stopped using NITDroid all-together, it is still very important to many of you.
there was an issue with it not working along side of the backupmenu application.
i just borrowed this post from Michal Jerz, owner of the 1st and oldest support/blog for symbian phones and many others dating back to 1999 and also very knowledgable of linux and the maemo devices call www.my-symbian.com or www.my-maemo.com or www.my-meego.com
here is his post with the solution to this issue where he deserves full credit.
http://my-symbian.com/forum/viewtopic.php?p=383405#383405
Posted: Friday, 31.Dec.2010 02:13 Post subject:
Quote:
Slightly off topic: I had to uninstall BackupMenu to install NITdroid - have you managed to get them working together, Michal?
Yes. It takes some work but it is doable.
1. Download these patched files to MyDocs and then type in XTerminal (after sudo gainroot) the following:
cd /sbin
tar -xzf /home/user/MyDocs/multiboot_patched.tar.gz
chmod 755 multiboot multiboot_read_item
2. Now create a new boot item for the boot menu. Using any text editor create a file with the following content:
ITEM_NAME="BackupMenu"
ITEM_SCRIPT="/usr/share/backupmenu/BackupMenuLauncher.item"
and save that file to /etc/multiboot.d/99-BackupMenu.item
3. You also need to make a symbolic link for evkey as it now be expected in a different location. Type in the X Terminal (after sudo gainroot):
ln -s /bin/evkey /usr/sbin/evkey
4. You also need to copy tar to the backupmenu directory. Type
cp /opt/maemo/usr/bin/gnu/tar /usr/share/backupmenu/
If you don't have tar installed then first type
apt-get install tar-gnu
That's probably all. Let me know if it works for you.

If you can advise how to resolve the issue, it would be GREAT!
I've got a 2GB MicroSD, standard issue that came with my daughters new Nokia phone, but she didn't need it (got a 4GB already). Not sure if this is a compatible one, as I've heard the OS can be funny with certain makes etc.
I've managed to "half" it (as far as Windows sees it, with a 1GB FAT partition now, in trying to format the card manually...But I think I've gone wrong...
Cheers!
If tnis post is a cure to your issue, please MARK IT AS SOLUTION.
If this post has helped anyone in any way, PLEASE SHARE YOUR KUDOS, by clicking on the GREEN STAR.

Tecra A11 - Win XP and Win 98 multiboot

Hi,
I would like do a multiboot XP / 98 on a TECRA A11.
Do you think it's possible.
Will I have some drivers dysfonction?
Thanks for answer !!

Well, Win XP installation should not be a big problem because the Win XP drivers seem to be available on Toshiba European driver page.
But Win 98 might be a problem here since its not supported and the drivers are not available you will need to search for such drivers at your hand and I think this might be a painful time I doubt you will be able to get Win 98 drivers because this OS is really, really old.
I would recommend installing the Win 98 only using Virtual Machine (VM) http://en.wikipedia.org/wiki/Virtual_machine
or Virtual PC
http://en.wikipedia.org/wiki/Windows_Virtual_PC
This is very easy running Win XP you can open virtual PC or VM and could start the Win 98

Multiboot kernel must be loaded before modules

Hello,
Does anybody knows what is the problem here.
kernel /I86PC.Solaris_10-1/multiboot kernel/unix - install dhcp -B console=ttya
,install_config=10.203.68.40:/opt/SUN/InstallServer/jumpstart,sysid_config=10.2
03.68.40:/opt/SUN/InstallServer/config/svr101,install_media=10.203.68.40:/opt/S
UN/InstallServer/sol10_8_07_x86,install_boot=::1:/opt/SUN/InstallServer/sol10_8
_07_x86/boot
module /I86PC.Solaris_10-1/x86.miniroot
Error 20: Multiboot kernel must be loaded before modules
It's jumpstart installation.
Thanks
Mario

I am getting similar error after upgrading my jumpserver form solaris 10 u2 to solaris 10 u6.
kernel /I86PC.Solaris_10-3/multiboot kernel/unix -B console=ttya,install_config
=10.2.11.240:/jumpserver/jumpstart,sysid_config=10.2.11.240:/jumpserver/Sysidcf
g/5.10u6/x86,install_media=10.2.11.240:/jumpserver/install/5.10u6/x86,install_b
oot=10.2.11.240:/jumpserver/boot/5.10u6/x86/Solaris_10/Tools/Boot
module /I86PC.Solaris_10-3/x86.miniroot
Error 20: Multiboot kernel must be loaded before modules
Press any key to continue..
ANY Suggestsion ?
Thanks,
W

T400 Boot problem

I have a strange boot problem: Whenever I reboot my T400, the machine freezes immediately after loading grub. (it passes the ThinkPad screen fine). I multiboot linux/win7, and this is not a grub problem, since when I boot Win7 the machine freezes somewhere in the windows loader, (the windows logo shows) and when I boot linux it freezes in the linux boot loader, with a blank screen, showing just a blinking underline. The disk seems ok too, since I can go for months having the machine sleep to RAM and resume without problem. It freezes only at boot, and the only way to get past it is to remove the power cable+battery/hold power button and pray. Any ideas for a more permanent solution?

loko, hello and welcome,
No answer, just questions: "whenever" you reboot - as in every time? And specifically _reboot_ as opposed to cold boot? Reboot from Win to Win, Lin to LIin, Win to Lin, Lin to Win? And warm reboot, or full power off, power on reboot?
When you reboot, is it always from an OS that has been fully shut down and _to_ an OS that has been previously fully shut down?
I've seen some pretty strange things happen when one reboots a hibernated OS where in the meantime the other OS has touched the file system. I wouldn't expect grub to care, unless this is grub2 - then who knows?
Also have seen some pretty strange stuff when warm rebooting from Linux to Windows. It can leave BIOS in a strange state. On my desktop, my NIC will be dead until I do a full cold boot - from AC mains off.
Just tossing *stuff* at the wall here,
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Lenovo 20157 Multi booting problem

Dear Team,
I have installed windows 8.1 & Ubuntu on Lenovo 20157 laptop, But its not work on multibooting mean when i disable UEFI boot settings that time ubuntu OS woring and its enable that time windows 8.1 working.So please give me solution for how i have choose one by one windows at booting time??
Regards,
Manoj
Solved!
Go to Solution.

Dear Team,
I think, Lenovo support team have not interest to solve customer problem..
Thanks for best support
Regards,
Manoj

Nitdroid Problem - Multiboot

Similar Messages

Maybe you are looking for