Re: Issues with xfree86

2005-01-22 Thread Michael Vang
Is it a PS/2 mouse?

If so, try 'modprobe mousedev' and 'modprobe psmouse' before trying to
start X... You can restart X by running '/etc/init.d/gdm restart' (or
xdm, whatever you are using), or you can just run startx... If these
work, add them to /etc/modules so they are loaded at startup
automatically...

If it is a USB mouse there are other modules that need to be loaded
depending on your hardware... uhci.hcd and/or ohci.hcd... You also
need mousedev and usbhid...

Mike (Xyzzy)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: USB mouse stops working intermittently with dmesg errors: drivers/usb/input/hid-core.c: input irq status -84 received

2005-01-20 Thread Michael Vang
On Wed, 19 Jan 2005 19:02:07 +0100, Ernest jw ter Kuile
<[EMAIL PROTECTED]> wrote:

> Yep, same here since last weeks upgrade to 2.6.10. Though here the mouse
> doesn't freeze, but reacts a bit slow at times.
> 
> I have a usb Logitech mouse, so apparently it's not hardware related.
> 
> also unplugging and replugging resolves.

I've had the same problem, but nothing shows up in /var/log/messages at all...

Well, if I unplug the mouse I get the -84 thing:

Jan 20 10:29:58 k8 kernel: drivers/usb/input/hid-core.c: input irq
status -84 received
Jan 20 10:29:58 k8 last message repeated 7 times
Jan 20 10:29:58 k8 kernel: usb 1-1: USB disconnect, address 2

I never thought to unplug the mouse and then plug it back in... I'm so
used to using a PS/2 mouse the thought never occurred to me!

Thanks for the tip!

Mike (Xyzzy)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Re: Re: "GRUB loading" problem with AMD64 install

2004-12-02 Thread Michael Vang
Just an interesting follow-up:
I replaced my Western Digital 80GB hard drive for 2 Seagate 80GB hard 
drives, and no longer is LBA or no LBA an issue... Everything works 
properly, no matter how I try to break it...

I have no idea why this is fixed now... I am using the same hardware and 
the same OS... I can only assume that something on that Western Digital 
hard drive was not programmed properly...

Mike (Xyzzy)



Re: Cool N' Quiet

2004-11-14 Thread Michael Vang
Andreas Richter wrote:
try a never kernel image. I use 2.6.9 and it works here.
Hmm... What am I doing wrong?
k8:~# modprobe cpufreq-userspace
k8:~# modprobe powernow-k8
FATAL: Error inserting powernow_k8 
(/lib/modules/2.6.9-9-amd64-k8/kernel/arch/x86_64/kernel/cpufreq/powernow-k8.ko): 
No such device

k8:~# ls -l /lib/modules/2.6.9-9-amd64-k8/kernel/arch/x86_64/kernel/cpufreq/
total 32
-rw-r--r--  1 root root  8889 2004-10-28 22:07 acpi.ko
-rw-r--r--  1 root root 17834 2004-10-28 22:07 powernow-k8.ko
k8:~# uname -a
Linux k8 2.6.9-9-amd64-k8 #1 Fri Oct 29 02:34:50 CEST 2004 x86_64 GNU/Linux
k8:~# mount
/dev/hda1 on / type reiserfs (rw,noatime,notail)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
Mike (Xyzzy)



Re: Installation report: Abit KV8 Pro / Athlon 64 3000+ / SATA

2004-10-29 Thread Michael Vang
John Chronakis wrote:
- VIA VT6122 on board gigabit lan was not detected. A quick google 
revealed that there is no support yet. Replaced with a realteck. 
WARNING: I had to disable on board lan from the BIOS, otherwise the 
installer was failing with an error (sorry don't remember the message)
And if you buy the non-Pro version (K8V) the onboard NIC works perfectly...
:)
Mike (Xyzzy)



Re: Recommended Graphics card for OpenGL (now is Matrox G450 / Athlon 64)

2004-10-28 Thread Michael Vang
Wolfgang Pausch wrote:
Does your g450 run without OpenGL/DRI on debian amd64? I mean, I´m content if 
I get X working, without 3d and similar things, in a reasonable high 
resolution like 1024x768.
G450 PCI here, no DRI, at 1152x864... Works fine for ordinary stuff...
Mike (Xyzzy)



Speaker beep...

2004-10-23 Thread Michael Vang
Ever since I switched to pure64, the speaker beep does not work... I 
don't enable the sound on my motherboard (K8V) so I rely on the speaker 
beep for some things...

It appears that the kernel is configured properly:
[EMAIL PROTECTED]:/$ cat /boot/config-2.6.8-9-amd64-k8 | grep SPKR
CONFIG_INPUT_PCSPKR=m
Mike (Xyzzy)



Re: Which kernel?

2004-10-21 Thread Michael Vang
John Chronakis wrote:
Why 2 different versions of kernels? Does the netinst image installs 2.4 
kernel.

I am currently away form this linux and unfortunatly I forgot to uname 
it so I do not know what kernel version 'linux' loads.
I installed on the 18th also...
Note that all 4 of those entries point to the same kernel... The only 
differences are the boot options and the "route" they take to get there...

title   Debian GNU/Linux, kernel 2.6.8-9-amd64-k8
root(hd0,0)
kernel  /boot/vmlinuz-2.6.8-9-amd64-k8 root=/dev/hda1 ro 
console=tty0
initrd  /boot/initrd.img-2.6.8-9-amd64-k8

title   Debian GNU/Linux, kernel
root(hd0,0)
kernel  /boot/vmlinuz root=/dev/hda1 ro console=tty0
initrd  /boot/initrd.img
Note the symbolic links:
lrwxrwxrwx   1 root root  24 2004-10-18 16:21 vmlinuz -> 
vmlinuz-2.6.8-9-amd64-k8

lrwxrwxrwx   1 root root  27 2004-10-18 16:21 initrd.img -> 
initrd.img-2.6.8-9-amd64-k8

[EMAIL PROTECTED]:~$ uname -a
Linux k8 2.6.8-9-amd64-k8 #1 Sun Oct 3 18:22:21 CEST 2004 x86_64 GNU/Linux
As for the error message you got when you tried "linux26", I believe 2.6 
is the one and only choice on the CD...

Mike (Xyzzy)



Re: Newbie question - installation problems

2004-10-20 Thread Michael Vang
Ray Lanza wrote:
I've just installed debian on an athlon 64 machine using the netinstall iso.
I have  my sources.list pointed towards debian-amd64.alioth.org/sarge/
testing.
Is this right?
Many of the things I try to install fail authentication, is that expected?
I'm real new to this, having just installed two days ago, but everything 
works great here...

[EMAIL PROTECTED]:~$ cat /etc/apt/sources.list
#deb http://debian-amd64.alioth.debian.org/pure64 sid main
deb http://debian-amd64.alioth.debian.org/pure64 unstable main
deb-src http://debian-amd64.alioth.debian.org/pure64 unstable main
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-10 Thread Michael Vang
Ron Johnson wrote:
I wonder if this is something to also be mentioned on LKML?
Apparently this might be a known issue... I can barely understand any of 
this:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=1Gjko-6Y1-5%40gated-at.bofh.it&rnum=4
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=WJ3h.3dk.1%40gated-at.bofh.it&rnum=4&prev=/groups%3Fq%3Dparted%2520kernel%25202.6%26hl%3Den%26lr%3D%26ie%3DUTF-8%26sa%3DN%26tab%3Dwg
Sorry for the long URLs...
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-10 Thread Michael Vang
Solved!

But, it isn't pretty...

This appears to be a K8V BIOS issue... In the BIOS, under the hard drive
section, there is an option for LBA... The choices are "auto" and
"disabled"... There is no option for "enabled"... Apparently, there is
no way, in the BIOS, to force LBA on...

Every time you boot the BIOS looks to see if the drive is formatted with
LBA enabled... If it is, LBA is turned on... If not, it is turned off...
You can view this at the second black boot screen, which lists all the
properties of the system... The screen where it asks you to hit  to
boot...

So, check this out:

-> Zero MBR (dd if=/dev/zero of=/dev/hda bs=512 count=1) and then
reboot... LBA is on...

-> Boot random Linux ISO... Using previously cleared MBR, make a
partition table and then reboot... LBA is off...

-> Boot Windows 98 floppy... Use floppy to write a new MBR (fdisk /mbr)
and then reboot... LBA is on...

What have we learned? Somehow, the Linux way of writing the partition
table is messing things up... So now what do we do?

-> Boot random Linux ISO... Using existing Windows MBR, make a new
partition... Format partition however you want and then reboot... LBA is
on...

Observe:

With no LBA:

Disk /dev/hda: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

With LBA:

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

They are both the same size but they have a different reported
geometry...

Anyways, I have rebooted several times to make sure that this works... I
have no idea what LBA is exactly, or why we need it, but it looks like
this is the problem... Hopefully Asus will release a new BIOS that
allows you to force LBA on...

Note there is an option in the installer for Debian to write a whole new
MBR... I think this option also causes this error...

I sure hope there is an easier solution!

Mike (Xyzzy)




Re: Asus K8V - acpi/cpufreq

2004-10-10 Thread Michael Vang
Anders Peter Fugmann wrote:
# I2C adapter drivers
i2c-isa
# I2C chip drivers
w83627hf
I tested the K8V in Windows for a few minutes and probed the chip as a 
W83697HF... I don't know if this changes anything from what you got...

From CPU-Z, version 1.24:
Sensor Chip Winbond W83697HF
Mike (Xyzzy)



Re: Asus K8V - acpi/cpufreq

2004-10-10 Thread Michael Vang
Sebastian Steinlechner wrote:
> I don't know about fan speed - both /proc/acpi/thermal_zone and
> /proc/acpi/fan are empty here, so I have no idea how to get the
> necessary information. On the other hand, the K8V bios has a "Q-Fan
> control" option that's supposed to do fan throttling. However, I don't
> know what thermal trip points it uses so I'm a bit worried to turn it
> on...
I tested Q-Fan earlier this week:
K8V, cheap OEM HSF, 3200+
Q-Fan on, system idle: The temp ocillates between 43C and 52C (This 
happens at 4-5min intervals)
Q-Fan on, system under load: The temp tops at 61C, then falls to 48C

Q-Fan off, system idle: 36.5C
Q-Fan off, system under load: 48C
It looks like there are only two fan speeds... The 9C variance at idle 
with Q-Fan turned on can't be good for the long term life of the CPU, 
since I've heard that thermal expansion and contraction are bad for CPUs...

I run my box 24x7 doing scientific calculations, so Q-Fan really doesn't 
matter for me... I do plan to get an Alpha 8150 HSF this week though...

Note that the numbers I listed above were with Cool'n'Quiet disabled...
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-09 Thread Michael Vang
Michael Vang wrote:
I'm starting to think this is an LBA issue...
http://groups.google.com/groups?hl=en&lr=&c2coff=1&threadm=x73c77vlfc.fsf%40bonnet.wsrcc.com.lucky.openbsd.tech&rnum=9&prev=/groups%3Fq%3Dk8v%2520lba%26hl%3Den%26lr%3D%26c2coff%3D1%26sa%3DN%26tab%3Dwg
Maybe this will help? I hope that url doesn't wrap... Hmm...
Maybe:
http://tinyurl.com/5mhk2
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-09 Thread Michael Vang
Michael Vang wrote:
The 6GB worked perfectly, so it must have something to do with the drive 
size, or maybe something like LILO's old 1024 cyinder limitation...
I'm starting to think this is an LBA issue...
When I boot, there is a black screen that the BIOS puts up, that lists 
the hardware... On the part that lists the HD, it says LBA is turned 
off, even though I have it set to "auto" in the BIOS... The BIOS 
mentions that it will use LBA if the HD supports it *AND* if the drive 
is formatted with LBA enabled... (?)

If I boot a set of debian floppies (RC1) the HD doesn't even show up... 
If I use the RC1 CD, it does...

I'm tempted to try this:
boot: linux hda=XXX,YYY,ZZZ
My disk, as reported by "fdisk -l":
Disk /dev/hda: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/hda1   *   1 194   97744+  83  Linux
/dev/hda2 1951163  488376   83  Linux
/dev/hda31164  15506177564592   83  Linux
More info:
http://www.faqs.org/docs/Linux-HOWTO/Large-Disk-HOWTO.html
http://www.ces.clemson.edu/linux/fc2.shtml
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-06 Thread Michael Vang
I wonder if these bug reports match our issue?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272625
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266049
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-06 Thread Michael Vang
Michael Vang wrote:
I plan to try the 6GB disk out again tonight, just to make sure!
The 6GB worked perfectly, so it must have something to do with the drive 
size, or maybe something like LILO's old 1024 cyinder limitation...

I thought it might be the fact that the first partition wasn't the boot 
partition, but I used just one partition, so by default that partition 
is the first...

Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-06 Thread Michael Vang
Eric Lacroix wrote:
Le mer 06/10/2004 à 18:33, Michael Vang a écrit :
I think it has something to do with the WD drive and the mobo... I have 
a small 6GB drive that works perfectly, and it is a Maxtor...
Don't you think it is related to the size of the partition only ?
What make you think it's an HD/Mobo problem ?
I have had weird problems with WD drives in the past, but I guess that 
isn't very scientific...

Check this out:
I forgot to mention that this A64 is new to me... I just built it this 
week... Anyways, when I had it finished I wanted to move my HD from my 
old box to the new one... I've done this hundreds of times and (unlike 
Windows) it usually works without a hitch... But, I got the Grub error! 
So it isn't just installing the Grub I don't think, because I booted 
that box a lot and Grub worked fine! The old box was an XP1800, and the 
HD had been swapped multiple times to a P3-600...

And check this out: I vaguely remember installing Ubuntu (default 
install) and it rebooted at the end, as expected... The system came up 
and it did all sorts of configuration stuff, then the system was up... I 
then apt-get updated and upgraded, and on the next boot it failed... I 
think I did this twice...

All told, I've installed (well, attempted mostly) Debian and Ubuntu 
close to 30 times in the last few days trying to find a common problem...

If there isn't a small partition at the front of the drive, and if I 
boot a Win98 boot floppy, it hangs... However, several of my other 
floppies will boot, such as my mprime floppy and my memtest86 floppy...

My guess is the Win98 floppy is "timing out" looking for a HD... Why I 
have no idea, but if I put a small partition in, the floppy works...

I'm running the 1004 BIOS... I had a hard time flashing the BIOS since I 
couldn't get the Win98 boot floppy to boot! Come to find out the K8V has 
a special mode to flash a BIOS without a boot disk...

I sure hope I can figure out what is wrong with this! I've torn the box 
down so many times... I've even swapped video cards from AGP to PCI 
thinking that might help... I read somewhere there was a bug on the K8V 
that caused it to have boot problems if the AGP aperture was set to 256MB...

I plan to try the 6GB disk out again tonight, just to make sure!
Mike (Xyzzy)



Re: "GRUB loading" problem with AMD64 install

2004-10-06 Thread Michael Vang
Ryan Verner wrote:
Hi,
Having a strange problem trying to install Debian AMD64 (downloaded
the latest CD).  I run through the normal installation, partition my
drive (79.5MB ext3 /, 512MB swap), all goes well, I reboot and GRUB
hangs at "GRUB loading, please wait...".
I've checked /boot/grub/menu.lst and it looks fine to me.
The machine has two hard drives; 80G hda (hda1, 80G NTFS WinXP), and
80G hdb (partitioned as above, hda1/hda2).  Grub is installing itself
onto /dev/hda, and I've even booted the CD into rescue mode, mounted
/, chrooted, ran grub-install, and it makes absolutely no difference.
When I tried to install ubuntu amd64, I ran into this exact same
problem, but for some strange reason on every 2nd identical install
grub would install perfectly.  This doesn't occur in this case.
The system is an Athlon64 3000+, on an ASUS K8V SE Deluxe motherboard.
 hda is a Seagate, hdb is a Western Digital.
I have the exact same problem with my K8V (non-deluxe)...
If I use a small /boot partition, it always works right, but I don't 
want to do that, and Ubuntu, by default, doesn't even set up a /boot...

I've tried all the different filesystems with the same errors...
I only have one HD, a WD 80GB...
I think it has something to do with the WD drive and the mobo... I have 
a small 6GB drive that works perfectly, and it is a Maxtor...

I've tried forcing the drive master, forcing it cable select and I have 
tried it with various jumper configs...

I sure hope we can figure this out! I'm willing to try stuff on this box 
if anyone has ideas...

Mike (Xyzzy)