Nothing happens after Freeloader timeout
Moderator: Moderator Team
Nothing happens after Freeloader timeout
Hi, I wanted to try ReactOS out on real hardware this time.
I formatted the first primary partition on the harddisk with FAT32, it is 40 GB big. I installed Reactos using the install CD.
I booted Freeldr via GRUB 2 using the following stanza:
set root=(hd0,msdos3)
chainloader +1
parttool (hd0,msdos3) boot+
multiboot /freeldr.sys
This is the Freeldr.ini:
[FREELOADER]
DefaultOS=ReactOS
TimeOut=10
[Operating Systems]
ReactOS="ReactOS"
[ReactOS]
TitleText=ReactOS
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(0)\REACTOS
Options=/DEBUGPORT=SCREEN
After the 10 sec timeout is complete, nothing happens. Freeldr just sits there idly. No error message, no nothing. Is there any obvious mistake in the config that I am overlooking?
I formatted the first primary partition on the harddisk with FAT32, it is 40 GB big. I installed Reactos using the install CD.
I booted Freeldr via GRUB 2 using the following stanza:
set root=(hd0,msdos3)
chainloader +1
parttool (hd0,msdos3) boot+
multiboot /freeldr.sys
This is the Freeldr.ini:
[FREELOADER]
DefaultOS=ReactOS
TimeOut=10
[Operating Systems]
ReactOS="ReactOS"
[ReactOS]
TitleText=ReactOS
BootType=ReactOS
SystemPath=multi(0)disk(0)rdisk(0)partition(0)\REACTOS
Options=/DEBUGPORT=SCREEN
After the 10 sec timeout is complete, nothing happens. Freeldr just sits there idly. No error message, no nothing. Is there any obvious mistake in the config that I am overlooking?
Re: Nothing happens after Freeloader timeout
Hi!
Thanks for testing ReactOS in RH.
May you check this link with suggestion in order to help you? Thanks!
viewtopic.php?f=4&t=13361
Thanks for testing ReactOS in RH.
May you check this link with suggestion in order to help you? Thanks!
viewtopic.php?f=4&t=13361
Re: Nothing happens after Freeloader timeout
I have now replaced BootType=Reactos with BootType=Windows2003 (as in the freeldr.ini shipped with the Virtualbox image)
Now, freedldr attempt to boot Reactos, but the screen remains empty, also tried debugging mode, command line mode, all to no avail.
Now, freedldr attempt to boot Reactos, but the screen remains empty, also tried debugging mode, command line mode, all to no avail.
Re: Nothing happens after Freeloader timeout
Thanks, but this really doesn't get me anywhere. I get nothing but a blank screen, also with debugging enabled.vicmarcal wrote:Hi!
Thanks for testing ReactOS in RH.
May you check this link with suggestion in order to help you? Thanks!
viewtopic.php?f=4&t=13361
- EmuandCo
- Developer
- Posts: 4734
- Joined: Sun Nov 28, 2004 7:52 pm
- Location: Germany, Bavaria, Steinfeld
- Contact:
Re: Nothing happens after Freeloader timeout
Debug Output without a serial Port is a bit of a problem. Try Debug (Screen). Asserts / Kernel Debugger wont be seen, but errors are shown.
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.
If my post/reply offends or insults you, be sure that you know what sarcasm is...
If my post/reply offends or insults you, be sure that you know what sarcasm is...
Re: Nothing happens after Freeloader timeout
You can also enable FreeLdr debugging (with serial only, though)...
Re: Nothing happens after Freeloader timeout
Tried with screen debugging (see above), but all I get is a blank screen. Given up for now...EmuandCo wrote:Debug Output without a serial Port is a bit of a problem. Try Debug (Screen). Asserts / Kernel Debugger wont be seen, but errors are shown.
Thanks and good luck!!
Re: Nothing happens after Freeloader timeout
Well, the link I gave you is not just about how to obtain a debuglog but also about how to properly report so we can really help you.j.rohr wrote:Thanks, but this really doesn't get me anywhere. I get nothing but a blank screen, also with debugging enabled.vicmarcal wrote:Hi!
Thanks for testing ReactOS in RH.
May you check this link with suggestion in order to help you? Thanks!
viewtopic.php?f=4&t=13361
To begin with, I still don't know if you're using a DAILY BUILD (with enhanced SATA support and enhanced partition management) or the old 0.3.16.
Since it seems to be a FreeLDR issue, the last "optional" point about giving us info of your hardware is probably a "must" have here.
Re: Nothing happens after Freeloader timeout
Well, as long as I don't see at least some error log, I thought that reporting hardware details was of little use.vicmarcal wrote:Well, the link I gave you is not just about how to obtain a debuglog but also about how to properly report so we can really help you.j.rohr wrote:Thanks, but this really doesn't get me anywhere. I get nothing but a blank screen, also with debugging enabled.vicmarcal wrote:Hi!
Thanks for testing ReactOS in RH.
May you check this link with suggestion in order to help you? Thanks!
viewtopic.php?f=4&t=13361
To begin with, I still don't know if you're using a DAILY BUILD (with enhanced SATA support and enhanced partition management) or the old 0.3.16.
Since it seems to be a FreeLDR issue, the last "optional" point about giving us info of your hardware is probably a "must" have here.
I was using release 0.3.16. I wasn't aware that there are daily builds with enhanced SATA support. The Lenovo 3000 N200 is a laptop, with SATA HD,
If it helps, here are the outputs of dmidecode, lspci and lsusb:
# dmidecode 2.12
SMBIOS 2.4 present.
25 structures occupying 1056 bytes.
Table at 0x000DC010.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: 68ET27WW
Release Date: 11/14/2007
Address: 0xE5740
Runtime Size: 108736 bytes
ROM Size: 1024 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/360 kB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 0.39
Firmware Revision: 0.39
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 0769BUG
Version: 3000 N200
Serial Number: XXXXXXXXXXXXXX
UUID: XXXXXXXXXXXXXXXXXXXXXXXXX
Wake-up Type: Power Switch
SKU Number: Lenovo
Family: Lenovo
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: LENOVO
Product Name: IEL10
Version: REFERENCE
Serial Number: XXXXXXXXXXXXXXX
Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
Manufacturer: No Enclosure
Type: Notebook
Lock: Not Present
Version: N/A
Serial Number: None
Asset Tag: No Asset Tag
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00001234
Handle 0x0004, DMI type 4, 35 bytes
Processor Information
Socket Designation: U2E1
Type: Central Processor
Family: Other
Manufacturer: Intel
ID: FD 06 00 00 FF FB EB BF
Version: CPU Version
Voltage: 3.3 V
External Clock: Unknown
Max Speed: 4096 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: ZIF Socket
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specifed
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 64 kB
Maximum Size: 64 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Asynchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 1024 kB
Maximum Size: 4096 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Burst
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: Circular DIN-8 male
Port Type: Keyboard Port
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS/2 Mouse
External Connector Type: Circular DIN-8 male
Port Type: Mouse Port
Handle 0x0009, DMI type 9, 13 bytes
System Slot Information
Designation: PCI Slot J8B1
Type: 32-bit PCI
Current Usage: Unknown
Length: Long
ID: 0
Characteristics:
5.0 V is provided
3.3 V is provided
Handle 0x000A, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Disabled
Description: HD-Audio
Handle 0x000B, DMI type 11, 5 bytes
OEM Strings
String 1: AhY4v-Pw6zrqX
String 2: V0U8VdEe3Lf3w
String 3: wsynhwi2QwMlS
Handle 0x000C, DMI type 12, 5 bytes
System Configuration Options
Option 1: SMI:00B2C1
Option 2: DSN: 018001CPCK40PB0GPXJ0
Option 3: DSN: EBE52UD6AHSA-6E-E 1ADADAE9
Option 4: DSN: SANYOLNV-42T451406103793
Option 5: TIM:
Handle 0x000D, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 1000 MB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x000E, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x000D
Error Information Handle: No Error
Total Width: 64 bits
Data Width: 64 bits
Size: 512 MB
Form Factor: SODIMM
Set: 1
Locator: M1
Bank Locator: Bank 0
Type: DDR2
Type Detail: Synchronous
Speed: 533 MHz
Manufacturer: Mfg 0
Serial Number: 1234-B0
Asset Tag: Not Specified
Part Number: SODIMM000
Handle 0x000F, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x000D
Error Information Handle: No Error
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: 1
Locator: M2
Bank Locator: Bank 1
Type: DDR2
Type Detail: Synchronous
Speed: 533 MHz
Manufacturer: Mfg 1
Serial Number: 1234-B1
Asset Tag: Not Specified
Part Number: SODIMM001
Handle 0x0010, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0009FFFFFFF
Range Size: 2560 MB
Physical Array Handle: 0x000D
Partition Width: 2
Handle 0x0011, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0001FFFFFFF
Range Size: 512 MB
Physical Device Handle: 0x000E
Memory Array Mapped Address Handle: 0x0010
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x0012, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00020000000
Ending Address: 0x0009FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x000F
Memory Array Mapped Address Handle: 0x0010
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x0013, DMI type 32, 20 bytes
System Boot Information
Status: <OUT OF SPEC>
Handle 0x0014, DMI type 131, 22 bytes
OEM-specific Type
Header and Data:
83 16 14 00 01 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 01
Strings:
TVT-Enablement
Handle 0x0015, DMI type 131, 22 bytes
OEM-specific Type
Header and Data:
83 16 15 00 01 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 01
Strings:
TVT-Enablement
Handle 0x0016, DMI type 133, 5 bytes
OEM-specific Type
Header and Data:
85 05 16 00 01
Strings:
KHOIHGIUCCHHII
Handle 0x0017, DMI type 135, 10 bytes
OEM-specific Type
Header and Data:
87 0A 17 00 50 54 07 03 01 05
Handle 0x0018, DMI type 127, 4 bytes
End Of Table
:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
06:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
08:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
08:06.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
08:06.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
08:06.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
lsusb:
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 04f2:b013 Chicony Electronics Co., Ltd USB 2.0 Camera
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Re: Nothing happens after Freeloader timeout
Thanks!
0.3.16 is old but stable, may you try this build http://iso.reactos.org/bootcd/bootcd-63542-dbg.7z to check if it solves your issues?
0.3.16 is old but stable, may you try this build http://iso.reactos.org/bootcd/bootcd-63542-dbg.7z to check if it solves your issues?
Re: Nothing happens after Freeloader timeout
I tried the latest nightly, r63586, here get a little further, i.e. freedoader actually loads the kernel and the booting process starts, but then ReactOS seems to hang loading the PCIIDE.sys. I tried debugging to a log file, but to no avail. So I photographed the boot screen instead,vicmarcal wrote:Thanks!
0.3.16 is old but stable, may you try this build http://iso.reactos.org/bootcd/bootcd-63542-dbg.7z to check if it solves your issues?
Here is the bootscreen:
[ external image ]
- EmuandCo
- Developer
- Posts: 4734
- Joined: Sun Nov 28, 2004 7:52 pm
- Location: Germany, Bavaria, Steinfeld
- Contact:
Re: Nothing happens after Freeloader timeout
Try installing ROS with NON ACPI HAL plz. I know that hang from one of my testing notebooks.
EDIT: See BUG https://jira.reactos.org/browse/CORE-7773
EDIT: See BUG https://jira.reactos.org/browse/CORE-7773
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.
If my post/reply offends or insults you, be sure that you know what sarcasm is...
If my post/reply offends or insults you, be sure that you know what sarcasm is...
Re: Nothing happens after Freeloader timeout
Tried. This indeed brings me past this point.EmuandCo wrote:Try installing ROS with NON ACPI HAL plz. I know that hang from one of my testing notebooks.
EDIT: See BUG https://jira.reactos.org/browse/CORE-7773
Now I can actually proceed to a real windows-style bluescreen. Yay!
Before you ask me: I have seen two different bluescreens, one said "BAD_POOL_HEADER", the other one I forgot, but these are obviously separate and possibly more complex issues. I'll look whether there is any log file.
Re: Nothing happens after Freeloader timeout
In the boot menu there's a debug to screen option which will help.
Re: Nothing happens after Freeloader timeout
Isn't it what he used (see pictures)?Frontier wrote:In the boot menu there's a debug to screen option which will help.
Who is online
Users browsing this forum: No registered users and 43 guests