[Cooker] [Bug 3649] [urpmi] Urpmi produces incorrect English error message

2003-04-04 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=3649





--- Additional Comments From [EMAIL PROTECTED]  2003-04-04 10:38 ---
Um - no.
  http://www.m-w.com/cgi-bin/dictionary?va=inexistent
Even if you don't like inexistent, non-existent is still wrong.
There is no hyphen in nonexistent.




--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
# urpmi --media "Mandrake 9.1,Mandrake Contrib 9.1" --auto-select 
trying to select inexistent medium "Mandrake Contrib 9.1" 
 
Should be 
trying to select non-existent medium "Mandrake Contrib 9.1"



[Cooker] [Bug 3644] [drakxtools] DrakConnect doesn't work if eth driver is compiled in

2003-04-03 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=3644





--- Additional Comments From [EMAIL PROTECTED]  2003-04-04 02:04 ---
Nope - the issue isn't the chipset, which works fine. It is drakconnect with
*built-in* drivers.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
Using SiS900 onboard ethernet, driver compiled in to kernel, DrakConnect
properly identifies the interface but then complains that no interface was
found. The correct message would be that the *driver/module* was not found.
After saying "no device found" it refuses to proceed and deletes all existing
net conf files.
Would be nice if drakconnect worked with built-in drivers.



[Cooker] [Bug 3644] [drakxtools] New: DrakConnect doesn't work if eth driver is compiled in

2003-04-02 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=3644

   Product: drakxtools
 Component: DrakConnect
   Summary: DrakConnect doesn't work if eth driver is compiled in
   Version: 9.1-29mdk
  Platform: PC
OS/Version: All
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Using SiS900 onboard ethernet, driver compiled in to kernel, DrakConnect
properly identifies the interface but then complains that no interface was
found. The correct message would be that the *driver/module* was not found.
After saying "no device found" it refuses to proceed and deletes all existing
net conf files.
Would be nice if drakconnect worked with built-in drivers.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



[Cooker] [Bug 2255] [drakxtools] Bad frequency ranges in /etc/X11/XF86Config-4 in mdk-9.1rc2

2003-03-27 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=2255





--- Additional Comments From [EMAIL PROTECTED]  2003-03-27 09:19 ---
The problem with changing the default refresh rate has nothing to do with the
video card. Older monitors, which are still in use, can be physically damaged by
setting a rate higher than they are capable of. The ranges in XF86Config-4 are
safe for most SVGA capable monitors. If your monitor is identified (through
EDID) *and* has an entry in the database specifying what it is capable of you
should get  a range that works well. Unfortunately many monitors (Tatungs, in my
experience) have incorrect info in the database that results in lower ranges
than the manufacturer actually suggests, or the monitor is not in the database
at all and gets the default. The fix is to make sure Mandrake has the specs for
your monitor *from the manufacturer spec sheet* (as opposed to a 'best guess').
If the monitor isn't listed then Mandrake is quite correct in assuming
worst-case and not allowing a range that could cause damage.

Reading the EDID alone doesn't give enough information to make a safe judgement
as to what ranges are safe. Especially on the multi-sync monitors that have
discreet settings per mode amd cannot do in-between values (Older NEC monitors,
for example).




--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
Using mandrake-9.1rc1. XFdrake generates these default ranges for 1024x768: 
 
   HorizSync 31.5- 57 
   VertRefresh 50-70 
 
Obviously, which these ranges it is impossible to get any refresh rate above 
70Hz. Since XFdrake does not allow one to choose the refresh rate, the default 
ranges should be larger, something like: 
 
   HorizSync 30- 70 
   VertRefresh 50-90 
 
Even 5+ year old cards like riva128 can do 85Hz at [EMAIL PROTECTED]



[Cooker] [Bug 3311] [kernel] the system reboots withour any reason, P4S8X, nvidia ti4200

2003-03-14 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=3311





--- Additional Comments From [EMAIL PROTECTED]  2003-03-14 11:30 ---
That's not a module parameter, it's a kernel parameter.
Needs to be in the append= line in /etc/lilo.conf (and run "lilo" after editing).



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
With Mdk 9.1 rc2 my system reboots twice a day at least without any reason.
Looking at the logs I got

kernel: agpgart: Unsupported SiS chipset (device id: 064
8), you might want to try agp_try_unsupported=1.

kernel: NTFS-fs warning (device 03:01): parse_options():
 Option iocharset is deprecated. Please use option nls= in the futu
re.

I have got a p4s8x motherboard with SIS648 chipset. I also use the nvidia
propriaritary drivers with a ti 4200.

I have tried to add agp_try_unsupported=1 in an option line in modules.conf and
I will tell you as soon as possible if it solved the problem.



[Cooker] [Bug 2155] [Installation] 9.1 RC1 & RC2 DMA disabled ???

2003-03-08 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=2155





--- Additional Comments From [EMAIL PROTECTED]  2003-03-08 23:15 ---
This is a duplicate of 2275.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
The hardware is "fit" for DMA, why is it disabled?

Feb 22 14:34:04 localhost kernel: VP_IDE: chipset revision 6
Feb 22 14:34:04 localhost kernel: VP_IDE: not 100%% native mode: will probe irqs
later
Feb 22 14:34:04 localhost kernel: VP_IDE: VIA vt8235 (rev 00) IDE UDMA133
controller on pci00:11.1
Feb 22 14:34:04 localhost kernel: ide0: BM-DMA at 0xfc00-0xfc07, BIOS
settings: hda:DMA, hdb:DMA
Feb 22 14:34:04 localhost kernel: ide1: BM-DMA at 0xfc08-0xfc0f, BIOS
settings: hdc:DMA, hdd:DMA
Feb 22 14:34:04 localhost kernel: hda: ST340823A, ATA DISK drive
Feb 22 14:34:04 localhost kernel: hdb: IC35L060AVER07-0, ATA DISK drive
Feb 22 14:34:04 localhost kernel: hda: DMA disabled
Feb 22 14:34:04 localhost kernel: blk: queue c039acc0, I/O limit 4095Mb (mask
0x)
Feb 22 14:34:04 localhost kernel: hdb: DMA disabled
Feb 22 14:34:04 localhost kernel: blk: queue c039adfc, I/O limit 4095Mb (mask
0x)
Feb 22 14:34:04 localhost kernel: hdc: LITEON DVD-ROM LTD122, ATAPI CD/DVD-ROM drive
Feb 22 14:34:04 localhost kernel: hdd: R/RW 8x4x32, ATAPI CD/DVD-ROM drive
Feb 22 14:34:04 localhost kernel: hdc: DMA disabled
Feb 22 14:34:04 localhost kernel: hdd: DMA disabled
Feb 22 14:34:04 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 22 14:34:04 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15
Feb 22 14:34:04 localhost kernel: hda: host protected area => 1
Feb 22 14:34:04 localhost kernel: hda: 78165360 sectors (40021 MB) w/512KiB
Cache, CHS=4865/255/63, UDMA(100)
Feb 22 14:34:04 localhost kernel: hdb: host protected area => 1
Feb 22 14:34:04 localhost kernel: hdb: 120103200 sectors (61493 MB) w/1916KiB
Cache, CHS=7476/255/63, UDMA(100)

My SPECS:
AMD XP 2200+
MSI KT4 Ultra K400/VT8235#
512 MB DDR(333) RAM



[Cooker] [Bug 2858] [drakxtools] XFdrake selects too low refresh rates in mandrake-9.1rc2

2003-03-06 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=2858





--- Additional Comments From [EMAIL PROTECTED]  2003-03-06 22:25 ---
The horizontal and vertical refresh rates are monitor dependent. If your monitor
is correctly identified then the range is set according to a table of values.
Some monitors are incorrectly listed (most Tatung monitors, for example). If you
don't specify your monitor correctly (like if you choose "standard VGA" or
"generic SVGA") the rates will be too low for any decent resolutions. If your
monitor is not detected then it either doesn't support EDID or isn't in the list
- there is nothing Mandrake can do about that. Send em details of your monitor
to get it added.
Changing the default range for non-identified monitors is not a good thing -
standard VGA and SVGA monitors (yes, there are still millions in use) can be
fried by using an incorrect rate.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
My video card can do [EMAIL PROTECTED]@85Hz. However, XFdrake always sets the vertical 
refresh rate range to 50-70. The default settings of 
 
HorizSync 31.5-57 
VertRefresh 50-70 
 
are very inadequate and should be something more realistic like this: 
 
HorizSync 30-70 
VertRefresh 50-90 
 
Currently, XFdrake has no option for setting the refresh rate.



[Cooker] [Bug 2764] [Installation] kernel-enterprise needed for mem=1024 on i8200 bit strange?

2003-03-06 Thread murrayr
http://qa.mandrakesoft.com/show_bug.cgi?id=2764





--- Additional Comments From [EMAIL PROTECTED]  2003-03-06 12:35 ---
Both kernel and kernel-enterprise *should* be installed. Kernel-enterprise adds
overhead (as in, makes your box run slower) to access the additional 125M that
the standard kernel cannot reach. Some people are willing to sacrifice 125M for
a faster system. Mandrake doesn't make that choice for you - you get to make it
yourself.
To clarify choice - choose standard kernel for speed, kernel-enterprise for full
use of memory. This is NOT a Mandrake-mandated trade-off, it's the nature of the
linux kernel.

The standard kernel only reports about 900M available *because that it is all it
can access*. It does NOT use 'all available memory'.
As for RedHat using all memory in a standard kernel (if they do) then they are
doing a disservice to all their users who don't have more than 900M - they are
forcing them to pay the price in performance for something they don't have.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
It is a bit curious that when mem=1024 two kernels get installed:
kernel and kernel-enterprise.

When booting with kernel only 896 MB memory is found. Trying to boot
with 'mem=1024' in grub does not succeed. The boot stops with error.

kernel-enterprise works and shows 127 MB HIGHMEM and 896 MB LOWMEM.

Why is not kernel-enterprise installed as default.
Or why not just make one kernel?



[Cooker] [Bug 2275] [kernel-2.4.21.0.pre4.10mdk] conflicting info from kernel and hdparm about DMA in mdk-9.1rc1

2003-02-24 Thread murrayr
https://qa.mandrakesoft.com/show_bug.cgi?id=2275





--- Additional Comments From [EMAIL PROTECTED]  2003-02-24 17:30 ---
The DMA disabled message is a known 2.4.x issue with some chipsets (Via, IIRC) -
it temporarily disables the DMA to do setup, then re-enables it. For some reason
(I don't follow 2.4.x kernel stuff very closely, so don't know what the reason
is), the re-enable is done silently. I thought Alan Cox had published a patch
for it, but I could be wrong.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
Run "dmesg | grep DMA" and the output is: 
 
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA 
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:DMA 
hda: DMA disabled 
hdb: DMA disabled 
hdc: DMA disabled 
hdd: DMA disabled 
hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=2434/255/63, 
UDMA(100) 
hdb: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, 
UDMA(100) 
 
 
The messages show DMA as disabled but the UDMA mode for each of hda 
and hdb is listed as 100. Why this contradiction ? 
 
Both "hdparm -i /dev/hda" and  "hdparm -i /dev/hdb" have this line: 
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 
which shows that DMA is indeed enabled !! This is supported by entries in 
/proc/ide/hd*/settings too. So why these kernel messages about DMA disabled 
?



[Cooker] [Bug 2064] [wine] Wine won't create its own socket

2003-02-21 Thread murrayr
https://qa.mandrakesoft.com/show_bug.cgi?id=2064





--- Additional Comments From [EMAIL PROTECTED]  2003-02-21 20:43 ---
It isn't wine directly - I'm using winex 2.2a from transgaming and just noticed
it doing the same thing (I don't do wine stuff very often). It also isn't a
kernel issue, since I'm using 2.5.62, not a Mandrake kernel.




--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
When running wine, it won't create its own socket

[EMAIL PROTECTED] ~]$ tail -n 1 bin/kazaa 
$ARTSCMD wine ~/.wine/fake_windows/Program\ Files/KaZaA\ Lite/Kazaa.exe
[EMAIL PROTECTED] ~]$ kazaa
wine: lstat /tmp/.wine-todd/server-301-17dbe8/socket : No such file or directory
[EMAIL PROTECTED] ~]$ vdir /tmp/.wine-todd/server-301-17dbe8/
total 0
-rw-r--r--1 todd todd0 Feb 20 13:55 lock
srwxr-xr-x1 todd todd0 Oct  2 18:44 socket.sav
[EMAIL PROTECTED] ~]$ vdir /tmp/.wine-todd/  
total 4
drwx--2 todd todd 4096 Feb 20 13:55 server-301-17dbe8
[EMAIL PROTECTED] ~]$ cp -a /tmp/.wine-todd/server-301-17dbe8/socket.sav
/tmp/.wine-todd/server-301-17dbe8/socket
[EMAIL PROTECTED] ~]$ kazaa
ArtsD is running
The command will execute through artsdsp
fixme:win32:PE_CreateModule Unknown directory 15 ignored
Loading required GL library /usr/X11R6/lib/libGL.so.1.4.500
err:win32:PE_fixup_imports No implementation for SHELL32.DLL.712 imported from
C:\Windows\System\comdlg32.dll, setting to 0xdeadbeef


Works regularly.  Exit, then try again:

[EMAIL PROTECTED] ~]$ kazaa
ArtsD is running
The command will execute through artsdsp
wine: lstat /tmp/.wine-todd/server-301-17dbe8/socket : No such file or directory

The full kazaa wrapper script is:
[EMAIL PROTECTED] ~]$ cat bin/kazaa 
#!/bin/sh
### Brad Laue
# Wrapper launching Kazaa through wine; traps /dev/dsp through the arts 
# daemon if KDE is running, working around a bug.
#
ARTSCMD=""
ARTSSTAT=`artsshell status | head -1 | awk '{print $3}'`
case $ARTSSTAT in
suspended)
echo "ArtsD is not running."
ARTSCMD="exec"
;;
busy)
echo "ArtsD is running"
ARTSCMD="artsdsp"
echo "The command will execute through $ARTSCMD"
;;
*)
echo "Meh"
ARTSCMD=""
;;
esac
$ARTSCMD wine ~/.wine/fake_windows/Program\ Files/KaZaA\ Lite/Kazaa.exe