Custom Query (16363 matches)
Results (1507 - 1509 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #959 | fixed | problems with BIOS reals beyond LBA boundary? | ||
| Description |
I observe the following problems with VirtualBox. An explanation that fits this problem patterns is that there is a problem with BIOS initiated reads beyond the LBA boundary of a disk.
Here is an explanation that fits the above problem pattern: in real mode, reads from disks that are beyond the LBA boundary (separate interface INT 0x10,AH=0x42 IIRC) is broken. FAT/NTFS MBR uses the AH=0x02 interface for everything beyond sector 1024*255*63. This fits all problem/no problems:
Side notes: Vmware is able to boot into ALL of the 3 cases were virtual box isn't able. For problem 4, I made sure to add the necessary drivers into the criticaldevice section of the windows registry. I'm not sure if I did that correctly, but what really indicates that there is a problem at a much lower level (bios level) is that, in problem 3 I'm not only unable to boot into windows, but also unable to boot into the recovery console. the recovery console refuses to load because HAL.dll is not found (as I said HAL.dll is likely to reside after the LBA boundary). My next test case is: format a plain NTFS disk, fill it up with to 8GB, and do a fresh win xp install. The result (if my thesis is correct) should be that NTLDR is not found, and booting dies. (will do that in about a week, I just filed this bug now so that this issues is known, and this knowledge isn't lost if for some reason I forget to do this) Of course, if you have further insight you are free to provide it. |
|||
| #1908 | obsolete | VirtualBox mute on alsa/dmix configuration | ||
| Description |
dmix is an alsa plugin for user space sound stream mixing. The problem is that when the "default" alsa audio device is routed through dmix, then applications that try to open "default" for recording fail as dmix is only an output plugin. In general, the trick is to set the input device to something besides from "default" for these applications ("null"/"hw:0,0" is an option). This is possible with VirtualBox by setting the VBOX_ALSA_ADC_DEV=".." variable. First suggestion: Replacing the error message 00:00:08.982 ALSA: Failed to open 'default' as ADC with something like 00:00:08.982 ALSA: Failed to open 'default' as ADC, set VBOX_ALSA_ADC_DEV environment variable. in alsaaudio.c. I had to read "audio_process_options/audio_get_conf_in" in audio.c closely to understand what the code is actually doing. Second suggestion: If the input device is unavailable, complain but don't go mute completely. I presume the user rarely cares about a working input stream but will most certainly care about a working output stream. The strategy for alsaaudio.c in alsa_init_in could be: call alsa_open for a second time but with "null" set as conf.pcm_name_in. |
|||
| #2302 | fixed | keys dead when remapped by xkb -> fixed in SVN | ||
| Description |
Xorg supports remapping keys via xkb. A typical way would be: Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" "therp:desktop"
Additionally we put the following line into /etc/X11/xkb/rules/base (or xorg in the same dir): therp:desktop = +therp(desktop) This teaches Xorg to treat the option string "therp:desktop" namely by resolving it to +therp(desktop). Further we need to add the line --p----- -m------ therp(desktop) to /etc/X11/xkb/symbols.dir And finally add a file called therp to /etc/X11/xkb/symbols with the following content: partial modifier_keys
xkb_symbols "desktop" {
key <AD11> { symbols[Group1]= [ parenleft, braceleft ] };
key <AD12> { symbols[Group1]= [ parenright, braceright ] };
key <AE09> { symbols[Group1]= [ 9, bracketleft ] };
key <AE10> { symbols[Group1]= [ 0, bracketright ] };
};
The effect of these lines is that the keys () and [] are swapped on the keyboard. I personally like that as I type round brackets more often and I like them to be accessible without the Shift modifier key. However, as soon as a key is touched by xkb, it goes dead for VirtualBox. Notice that 0 and 9 wasn't changed, however 0 and 9 don't work even unshifted. To make it work I have to adjust the layouts manually in the vbox source code and supply vbox with a keymap that resembles my remappings precisely. |
|||

