Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
09-25-2002, 03:37 PM
|
#16
|
Member
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344
Rep:
|
Hi
for some extra info on your konsole-noxft;
http://www.mail-archive.com/expert@l.../msg56502.html
seems to be a mandrake upgrade issue. You upgraded kde to 3 i guess? I tried the kde 3 in redhat 7.3; there is no
konsole-xft around, but it works without errors. Why not use
aterm or eterm, they are much smaller and nicer looks once
you set up things in .Xdefaults
Ok enough on that one, to get back on your burner; your
scsi-emu seems to work, but does not recognise your device.
That is not an fstab issue. You need to make sure that the kernel knows that your hdd needs that.
So doublecheck your lilo.conf for the append="hdd=ide-scsi"
no typos ? you did rerun lilo afterwards ? and hdd is the
slave device on second ide?
Once you boot with that, your dmesg|less shows the append lines under
Kernel command lines;
ide_setup: hdd=ide-scsi
and a little later your burner inf string under
scsi0: scsi hostadapter bla bla bla
One thing on your /etc/fstab line; use scd0 not hdd;
cdrecord -scanbus will show your burner, but you can't
mount it, it produces an io error. -at least on my machine,
i tried some stuff on it, breaking things, just to check-
well i am out of thoughts right now, any one else ?
good luck
Last edited by mrGee; 09-25-2002 at 03:40 PM.
|
|
|
09-25-2002, 05:28 PM
|
#17
|
Member
Registered: Mar 2002
Location: Lausanne, Switzerland
Distribution: Mandriva 2007.0
Posts: 233
Original Poster
Rep:
|
Going to use another terminal now in KDE 3, thanks.
The burner is still not working, the entry, scsi: hostadapter etc... does not show any reference to my burner at all!???
|
|
|
09-26-2002, 04:59 PM
|
#18
|
Member
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344
Rep:
|
hi again
maybe post the output for the following things here, right
after you boot up your machine
your /etc/lilo.conf
dmesg|grep CD
your /etc/fstab
maybe some options block other things
no postings; but check /var/log/messages for errors
well you could post the errors that might look interresting
and look into /etc/sysconfig/hwconf ; the cdrom entry/entries
maybe firing up kudzu or harddrake detects your cdwriter
and makes the right entry somewhere. Do a man kudzu
it refers to your /etc/sysconfig/hwinfo file
(firing up kudzu on my box tries to mess up my mouse and
blackbox)
for further reading;
http://www.mandrakeuser.org/docs/hardware/hbits8.html
http://www.club-nihil.net/mub/viewto...hlight=idescsi
the last one is more a defs=mount issue concerning mount
errors
And i saw your kernel suggestion in another thread, it
shouldn't be necessary.
regards
|
|
|
09-29-2002, 11:14 AM
|
#19
|
Member
Registered: Mar 2002
Location: Lausanne, Switzerland
Distribution: Mandriva 2007.0
Posts: 233
Original Poster
Rep:
|
Thanks for not abandoning me: Here are relevant sections from the files suggested.
/etc/lilo.conf
disk=/dev/hde bios=0x81
image=/boot/vmlinuz
label=linux
root=/dev/hde1
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only
dmesg|grep cd = no output at all, the prompt reappears with a crlf.
/etc/fstab
/dev/hde1 / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hde7 /home ext3 defaults 1 2
/mnt/cdrom /mnt/cdrom supermount dev=/dev/hdd,fs=iso9660,--,defaults 0 0
/mnt/floppy /mnt/floppy supermount dev=/dev/fd0,fs=vfat,--,iocharset=iso8859-15,umask=0,sync,codepage=850 0 0
|
|
|
09-29-2002, 01:50 PM
|
#20
|
Member
Registered: Sep 2002
Distribution: Debian
Posts: 69
Rep:
|
is there a way of looking at all the messages you get when you first boot to check that linux is seeing cdrw as hdd and not something else?
|
|
|
09-29-2002, 03:06 PM
|
#21
|
Member
Registered: Mar 2002
Location: Lausanne, Switzerland
Distribution: Mandriva 2007.0
Posts: 233
Original Poster
Rep:
|
Yes I'm sure that there is a start-up log file somewhere as I'm going dizzy reading the screens during the boot! I have however seen my disks as:
hda: my 20Gb windoze disk
hde: my 40Gb linux udma100 disk
hdd: cdr-w correctly identified.
any other ideas welcome...
from dmesg | less I get:
/dev/ide/host0/bus0/target0/lun0: p1 p2 <p5>
/dev/ide/host2/bus0/target0/lun0: [PTBL] [4865/255/63] p1 p2 <p5 p6 p7>
Can't find anything else of interest.
Last edited by rooman; 09-29-2002 at 03:10 PM.
|
|
|
09-29-2002, 03:15 PM
|
#22
|
Member
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344
Rep:
|
Hi
some quick info/remarks
dmesg|grep CD ; cd in CAPITALS or use grep -i cd, brings
up more not so usefull info
and in general dmesg|less shows all kernel messages right
after boot.
See also /var/log/messages the bottom part ( this can be a very large file)
The kernel needs a scsi emu; well from the above messages
that thing looks allright. But it refuses to detect your burner right now.
Your burner is still working in winbloze for inst.? (just check
to exclude hardware faillures) And the jumper is set to slave
not to cable select, see also another thread on this;
http://www.linuxquestions.org/questi...226#post148226
still am clueless a bit
good luck
--hah some things seems to get answered already whilst i s_l_o_w_l_y type ahead, thanks rooman for the dmesg
thing  --
Last edited by mrGee; 09-29-2002 at 03:19 PM.
|
|
|
09-30-2002, 03:23 PM
|
#23
|
Member
Registered: Mar 2002
Location: Lausanne, Switzerland
Distribution: Mandriva 2007.0
Posts: 233
Original Poster
Rep:
|
dmesg|grep CD gives me:
hdd  roduct_name_of_cd-writer
hdd:short_description_eg:ATAPI cd writer 32X etc.
2 lines starting with hdd, does this mean anything useful, I'm starting to feel a bit numb in the brain?
ps: It works fine in windoze, going to check that it's not jumpered as cable select (as in other post "kabads")
|
|
|
09-30-2002, 03:42 PM
|
#24
|
Member
Registered: Sep 2002
Distribution: Debian
Posts: 69
Rep:
|
Mine was fixed in the end by a simple typo problem - 9600 instead of 9660 - simple really. Did you look at my modem doc ( www.monkeez.co.uk/linux/cd-rw.php)? It may or may not be the same for you, but it might also get you to check something else (modules.conf?)
|
|
|
10-01-2002, 03:58 PM
|
#25
|
Member
Registered: Mar 2002
Location: Lausanne, Switzerland
Distribution: Mandriva 2007.0
Posts: 233
Original Poster
Rep:
|
Thanks for your suggestions;
everything that everyone has suggested is correct in every file.
The burner still works fine in win2k.
Not detected by cdrecord etc.
Changed jumper to master, no changes, just detected as hdc now.
What next? Can anyone persuade me:
1. not to reinstall mdk8.2?
2. not to go back to win2k?
|
|
|
10-01-2002, 04:13 PM
|
#26
|
Member
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344
Rep:
|
Hi
well i have to admit; this one has got me stumped.
If this is a poll i would vote for 1 , tho reinstalling
linux is against my religion
The jumper changing check was really meant for
checking cable select/ slave .
As far as i see it something's wrong with your kernel and i
cannot see what. Scsi-emu there; won't detect your drive
weird. The entry /scd0 in fstab has only effect after the kernel
detects your writer.
whatever you decide; good luck
maybe someone sees a solution in time.
|
|
|
10-01-2002, 04:16 PM
|
#27
|
LQ Addict
Registered: Dec 2001
Location: Brooklyn, NY
Distribution: *NIX
Posts: 3,704
Rep:
|
did you fix you fstab entry
Code:
/mnt/cdrom /mnt/cdrom supermount dev=/dev/hdd,fs=iso9660,--,defaults 0 0
to have dev=/dev/scd0 or whatever it is now. Also post the output of
/sbin/lsmod
|
|
|
10-01-2002, 04:29 PM
|
#28
|
Member
Registered: Mar 2002
Location: Lausanne, Switzerland
Distribution: Mandriva 2007.0
Posts: 233
Original Poster
Rep:
|
The fstab entry is ok.
Here are the 2 relevant lines from lsmod:
ide-scsi 8032 0
scsi-mod 92488 2 [sg ide-scsi]
Don't waste too much time on this one, I'll reinstall in a day or so if nothing works.
|
|
|
10-02-2002, 11:28 AM
|
#29
|
Member
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344
Rep:
|
Hi
neo77777, good to see you dropped in, cause this one
does not look so simple, well at least to me it doesn't.
The fstab entry is not the issue right now.
It's the kernel not detecting the drive, as roomans dmesg dump shows. The scsi emu seems to work allright.
For burning only you don't need the fstab entry anyway,
cause it is burning unmounted. I tried it, by deleting the
entries for my cdrom's in fstab; after boot up it just works fine, and the mounting can then be made by hand.
Maybe you can see the kernel/scsi-emu problem, i might
have overlooked something obvious.
good luck
|
|
|
10-02-2002, 01:55 PM
|
#30
|
Senior Member
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
|
Maybe if we start from the beginning. . .
in /usr/sr/linux
make menuconfig
go to
IDE, ATA and ATAPI Block devices
Make sure SCSI emulation is built in to the kernel, not a module (the
problem with a module here is that the kernel may not know you want to
assign this as a SCSI device if it doesn't know how to deal with SCSI
emulation from the get-go). This of course requires that you have SCSI
support built into the kernel.
go to
SCSI support
Make sure you have Generic SCSI as either a module or built in.
Make sure you have SCSI CD-ROM as either a module or built in.
if you have to, rebuild your kernel
make dep&&make bzImage&& make modules && make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz.scsi
Make sure /etc/lilo.conf has the new kernel included
Make sure /etc/lilo.conf has the append="hdd=ide-scsi" line
lilo
reboot, see if you get something similar to (use dmesg | grep -i scsi):
ide_setup: hdd=ide-scsi
and
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Type: CD-ROM ANSI SCSI revision: 02
If you get that, do a
cat /proc/scsi/scsi
I've skipped a couple steps because I'm assuming you know how to build
a kernel, etc. If not, you should read up on how to do that before following
this too closely, especially since your distro may have some additional
gotchas.
|
|
|
All times are GMT -5. The time now is 12:12 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|