You Guys Rock!
Hello, I just wanted to take the time to thank you folks, especially Andrew and Bruce, who helped me overcome my installation problems. This list is a great resource for anyone interested in linux, and you guys just generally rock! Thank you! Best Wishes, Manu
Xserver can't find the mouse
Hello! The cdrom finally mounts! Thanks Bruce! But... believe it or not, what actually worked was when I accidentally typed: mount sonycd /cdrom!?!?! ls /dev/sonycd still comes up empty, but the cdrom works. Im sure this is probably bad, but I was so happy it finally worked I didnt want to question it. So I went ahead and used dselect to install a number of packages, including the ones for X windows (was I bad?). I was able to find all the information for the monitor, video card, etc. and the Xf86config seemed to go fine. But now the xserver cant find the mouse! I got the final error messages at the end after typing startx (the rest of the messages are given further below): System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 - R/usr/X11R6/lib/X11/xkb -xkm -m us -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 compiled/xfree86.xkm' Fatal server error: Cannot open mouse (No such file or directory) When reporting a problem related to a server crash, please send the full server output, not just the last messages X connection to :0.0 broken (explicit kill or server shutdown). When I looked for /dev/mouse (or just plain mouse) with ls no such file was found, and MAKEDEV gives the message dont know how to make device mouse. The mouse itself is nothing special just a microsoft standard serial mouse. :-( Is there an additional package or file I need to install, or do you think this has to do with my cdrom problem? Thanks for all your patient help :-) Best Wishes, Manu Script started on Sat May 6 18:17:15 2000 Agape:~# startx XFree86 Version 3.3.4 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: July 13 1999 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.36 i686 [ELF] Configured drivers: SVGA: server for SVGA graphics adaptors (Patchlevel 0): NV1, STG2000, RIVA 128, RIVA TNT, RIVA TNT2, RIVA ULTRA TNT2, RIVA VANTA, RIVA ULTRA VANTA, RIVA INTEGRATED, ET4000, ET4000W32, ET4000W32i, ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100, et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33, gvga, ati, sis86c201, sis86c202, sis86c205, sis86c215, sis86c225, sis5597, sis5598, sis6326, sis530, sis620, tvga8200lx, tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000, tvga9000i, tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi, tgui9430dgi, tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682, tgui9685, cyber9382, cyber9385, cyber9388, cyber9397, cyber9520, cyber9525, 3dimage975, 3dimage985, cyber9397dvd, blade3d, cyberblade, clgd5420, clgd5422, clgd5424, clgd5426, clgd5428, clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480, clgd5462, clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235, clgd7541, clgd7542, clgd7543, clgd7548, clgd7555, clgd7556, ncr77c22, ncr77c22e, cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag200, mgag100, mgag400, oti067, oti077, oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308, ali2401, cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv, ark2000pv, ark2000mt, mx, realtek, s3_virge, AP6422, AT24, AT3D, s3_svga, NM2070, NM2090, NM2093, NM2097, NM2160, NM2200, ct65520, ct65525, ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550, ct65554, ct6, ct68554, ct69000, ct64200, ct64300, mediagx, V1000, V2x00, p9100, spc8110, i740, i740_pci, Voodoo Banshee, Voodoo3, generic (using VT number 7) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keymap: xfree86(us) (overrides other XKB settings) (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200 (**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms) (**) SVGA: Graphics device ID: WD90C31 (**) SVGA: Monitor ID: NEC Multisync 3Ds (--) SVGA: Mode 640x400 needs hsync freq of 43.27 kHz. Deleted. (--) SVGA: Mode 1152x864 needs hsync freq of 43.92 kHz. Deleted. (--) SVGA: Mode 800x600 needs hsync freq of 48.08 kHz. Deleted. (--) SVGA: Mode 1024x768 needs hsync freq of 48.36 kHz. Deleted. (--) SVGA: Mode 640x480 needs hsync freq of 53.01 kHz. Deleted. (--) SVGA: Mode 1152x864 needs hsync freq of 53.51 kHz. Deleted. (--) SVGA: Mode 800x600 needs hsync freq of 55.84 kHz. Deleted. (--) SVGA: Mode 1024x768 needs hsync freq of 56.48 kHz. Deleted. (--) SVGA: Mode 1280x1024 needs hsync freq of 51.02 kHz. Deleted. (--) SVGA: Mode 800x600 needs hsync freq of 64.02 kHz. Deleted. (--) SVGA: Mode 1024x768 needs
Re: Now Can't Mount the CDROM
Hello!
Bruce, thanks for the tip about script. For whatever reason, man
didnt work, but I got the script working anyway. Here are the relevant
excerpts:
Agape:~# ls -l /dev/{sonycd,cdrom}
ls: /dev/{sonycd,: No such file or directory
ls: cdrom}: No such file or directory
Agape:~# /dev/MAKEDEV sonycd
Agape:~# ln -s /dev/{sonycd, cdrom}
Agape:~# mount /dev/sonycd /cdrom
mount: /dev/sonycd is not a block device
Agape:~# mount /dev/cdrom /cdrom
mount: special device /dev/cdrom does not exist
Agape:/etc# ae fstab
File fstab 345 bytes read.
7m5...105...205...305...405...505...60
5...705...80 /etc/fstab: static file system information.
#
# file system mount point type options dump pass
/dev/hda2 /ext2 defaults,errors=remount-ro
/dev/hda3 none swap
proc/procproc defaults
EOF
Agape:/etc# lsmod
Module Size Used by
cdu31a 21448 0 (unused)
serial 18412 0
parport_pc 5492 1 (autoclean)
lp 5184 0 (unused)
parport 6600 1 [parport_pc lp]
vfat8972 0 (unused)
smbfs 24104 0 (unused)
binfmt_aout 3668 0
Will I have to add some information to fstab, then? Thanks! - Manu
In a message dated 5/4/00 1:58:15 PM EST, [EMAIL PROTECTED] writes:
n Wed, 3 May 2000 [EMAIL PROTECTED] wrote:
Thanks everyone for your help so far. I was able to get the cdrom
module
installed by using modconf. Now, however, I can't get the cdrom to mount,
and the archives and howtos are of no help. Using the normal mount
command,
I get special device does not exist or sonycd is not a block device,
basically no matter what. The same thing happens when trying to install
applications from dselect: nothing I type in is recognized as a block
device.
This is on a 486 with a Sony CDU33A cdrom. Using lsmod the device driver
for the cdrom does show up.
Any tips/strategies? Thank you!
You are not really giving enough information, look at man script to
find out how to capture what you are doing in a file you can include in
your messages to the list.
What is the output of ls -l /dev/{sonycd,cdrom}?
(To make sure that the node for the sonycd device exists,
and cdrom is linked to it. Do a, /dev/MAKEDEV sonycd as root,
if it doesn't exist; do, ln -s /dev/{sonycd,cdrom} if there is no
link between the two.)
When you do a mount ... command;
what are the ... bits and what is the output?
(There are different mount command forms, some require fstab to be setup
properly in order to work.)
What does your /etc/fstab look like?
(This can affect what ... could be, and sets up some permissions and
access parameters.)
later,
Bruce
Re: Now Can't Mount the CDROM
Hi Bruce,
Im grateful for your help. It seems as though the problem
is there is no /cdrom directory or files! Do you know how I can
fix this? Perhaps load a disk image onto a floppy, or...?
Thanks!
- Manu
Here's the latest script:
Agape:~# mount /dev/sonycd /cdrom
mount: /dev/sonycd is not a block device
Agape:~# ls -l /dev/sonycd /dev/cdrom
ls: /dev/cdrom: No such file or directory
total 0
brw-rw 1 root disk 15, 0 May 5 20:37 sonycd-
Agape:~# ls -l /dev/cdrom
ls: /dev/cdrom: No such file or directory
Agape:~# /dev/MAKEDEV /cdrom
/dev/MAKEDEV: don't know how to make device /cdrom
Agape:~# /dev/MAKEDEV cdrom
/dev/MAKEDEV: don't know how to make device cdrom
Agape:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# file system mount point type options
dump pass
/dev/hda2 / ext2 defaults,errors=remount-ro 0
1
/dev/hda3 none swap sw 0
0
proc/proc proc defaults 0
0
/dev/cdrom /cdromiso9660 defaults,ro,user,noauto
0 0
Agape:~# ln -s /dev/sonycd /dev/cdrom
Agape:~# mount /dev/sonycd /cdrom
mount: /dev/sonycd is not a block device
Agape:~# exit
exit
Script done on Fri May 5 21:21:37 2000
In a message dated 5/5/00 9:07:46 PM EST, [EMAIL PROTECTED] writes:
Hello!
Bruce, thanks for the tip about script. For whatever reason, man
didnt work, but I got the script working anyway. Here are the relevant
excerpts:
Agape:~# ls -l /dev/{sonycd,cdrom}
ls: /dev/{sonycd,: No such file or directory
ls: cdrom}: No such file or directory
Ack! Try: ls -l /dev/sonycd /dev/cdrom
a{b,c} == ab ac, or at least it is if bash is the shell
...
Agape:/etc# ae fstab
File fstab 345 bytes read.
7m5...105...205...305...405...505...60
5...705...80 /etc/fstab: static file system information.
#
# file system mount point type options dump pass
/dev/hda2 /ext2 defaults,errors=remount-ro
/dev/hda3 none swap
proc/procproc defaults
Hmmm, where are the dump and pass flags; there should be 0 1 at the
end of the /dev/hda2 line, and 0 0 at the end of the others. Also,
try cat /etc/fstab, instead of ae fstab.
You could add:
/dev/cdrom /cdrom iso9660 defaults,ro,user,noauto 0 0
Agape:/etc# lsmod
Module Size Used by
cdu31a 21448 0 (unused)
serial 18412 0
parport_pc 5492 1 (autoclean)
lp 5184 0 (unused)
parport 6600 1 [parport_pc lp]
vfat8972 0 (unused)
smbfs 24104 0 (unused)
binfmt_aout 3668 0
This looks ok. I think your problem is that there is no node in
/dev for the sonycd (cd /dev;./MAKEDEV sonycd should fix it, but I
can't say for sure without seeing the output of the ls command given
earlier).
This is what it looks like on my system:
# ls -l /dev/sonycd /dev/cdrom
lrwxrwxrwx 1 root root 11 Mar 7 21:53 /dev/cdrom - /dev/sonycd
brw-rw 1 root root 15, 0 Feb 12 00:20 /dev/sonycd
later,
Bruce
Now Can't Mount the CDROM
Hi, Thanks everyone for your help so far. I was able to get the cdrom module installed by using modconf. Now, however, I can't get the cdrom to mount, and the archives and howtos are of no help. Using the normal mount command, I get special device does not exist or sonycd is not a block device, basically no matter what. The same thing happens when trying to install applications from dselect: nothing I type in is recognized as a block device. This is on a 486 with a Sony CDU33A cdrom. Using lsmod the device driver for the cdrom does show up. Any tips/strategies? Thank you! Best Wishes, Manu In a message dated 5/3/00 2:48:48 AM EST, [EMAIL PROTECTED] writes: I mean, which Compact Disc vendor (CheapBytes, O'Rielly, etc.). It's O'Reilly. I was able to successfully install and configure the base system by using floppies (I needed the drivers disk and the 8 base 14 floppies). However, no module worked for my CD-ROM drive. The closest one was the Sony CDU31A, but it didn't work (I got a device in use and two syntax error messages). Does anyone have any suggestions for how to get the system to recognize the CD-ROM drive now? That is the correct driver, it works for both cdu31a and cdu33a using /dev/sonycd. As root: lsmod will tell you if the sonycd.o module is already installed, if grep sonycd /boot/System.map* gets lot of hits then the driver is compiled into the kernel.
Re: Proprietary CD ROM Controller
Hi Bruce, Thanks for your reply! Unfortunately, the command didn't work and the help screen showed nothing similar. The help screen said that modules for proprietary controllers could not be loaded at boot, but only later. The problem is how can I load it later if it won't recognize the CD-ROM? I get through all the partitioning process fine, but when it comes to install the OS kernel and modules it can't get to them on the CD. Is there some way to get the needed files and modules onto floppy and install it from there? Thanks for your help! Best Wishes, Manu In a message dated 4/30/00 1:52:20 PM EST, [EMAIL PROTECTED] writes: Try passing the port and irq at the boot prompt (i.e., boot from a rescue floppy or through DOS using loadlin). The believe the syntax is: sonycd=I/O port,irq The default port is 0x320 (but check the interface to see where the jumpers are set) and irq is 0 (that is, no irq used). Check the help text (F1, F2, etc.) available through the first screen that comes up when you start the installation to make sure I have the syntax correct. - Bruce
Re: Proprietary CD ROM Controller
In a message dated 4/27/00 10:26:10 PM EST, [EMAIL PROTECTED] writes: In that portion of the install (You will have to make the rescue and root floppies as well as the driver floppies)... where it asks you to load Excuse the clueless question (I'm a total newbie at this) but although I made a boot disk, how do I make a root and driver floppy? :-) modules, the modules for sony-cd's are in there somewhere. I think under cd-rom (not for IDE CDROMS). I know this drive is supported (95% Sure). Yes, according to the web site it is supported. Thanks! - Manu I'm in the process of trying to install Debian from CD (I bought the package in a store) on a 486/66, with the eventual goal of being independent of the evil Gatesoft empire :-) But my problem is I have a SONY CDU33A CD-ROM which uses a Sony Proprietary controller, and the installation program doesn't see it and won't read from the CD-ROM. Does anyone have any tips for getting the installation program to recognize the CD-ROM? Thans for your help! Best Wishes, Manu
Proprietary CD ROM Controller
Hi All, I'm in the process of trying to install Debian from CD (I bought the package in a store) on a 486/66, with the eventual goal of being independent of the evil Gatesoft empire :-) But my problem is I have a SONY CDU33A CD-ROM which uses a Sony Proprietary controller, and the installation program doesn't see it and won't read from the CD-ROM. Does anyone have any tips for getting the installation program to recognize the CD-ROM? Thans for your help! Best Wishes, Manu
