On Sunday 27 January 2002 17.16, FX Fraipont wrote:

My CDR/RW id dev/sr0, and not /dev/scd0

They are exactly the same. Both are block major 11, minor 0. //Anders

I'm using Suse 7.3 with all the latest patches and updates. Using KDE 2.2.2, kernel 2.4.16 and Interbase 6.01 that comes with K1 Desktop Developer Companion CD. I am getting an error message trying to start the Interbase 601 database server. I get the following error message: "Unable to complete network request to host "localhost". Failed to establish a connection. Connection refused." This error message also happens when using ibmgr (the program that starts Interbase directly from the command line. My network connection is via cable modem using dhcp. I noticed that the file /etc/resolv.conf does not have a localhost line in it. Is this necessary when using dhcp? I modified the appropriate files so that dhcpcd would not change /etc/resolv.conf. As per the comments in resolve.conf. Also added an entry for localhost. Am able to ping localhost, 127.0.0.1 and 24.x.x.x, the localhost alias setup by dhcpcd and the cable modem. If I want to use Interbase, do I need to use a static internet (no dhcp) connection and add localhost? When I change to a static connection, I can start Interbase, but I have no internet connection. When I use dhcpcd for a dynamic connection, I can't start Interbase. Ideally I would like to use local Interbase along with Kylix and a DHCP internet connection for my cable modem. I previously posted to borland.public.kylix.sqlservers newsgroups on newsgroups.borland.com under the thread "Interbase and 'localhost not found' ". Unfortunately, none of the help offered there did anything to solve the problem. Any ideas ? TIA

On Sunday 27 January 2002 17:16, FX Fraipont wrote:

I'm using a creative cdr cdrw on my box running SuSE 7.1 and a self-compiled 2.4.17 kernel.

I'm curious. Do you use an initrd file? Do you have a /boot/initrd or /boot/initrd.suse and do you have a line in your /etc/lilo.conf that looks like 'append = "initrd = /boot/initrd"'?

My CDR/RW id dev/sr0, and not /dev/scd0

/dev/scd0 has worked for me before though, and when I use /dev/sr0 in the mount command, I get the same error message.

Compile options are

IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDESCSI=m CONFIG_BLK_DEV_CMD640=y CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_ADMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_PCI_AUTO=y

These are about what Ihave compiled into the self-compiled 2.4.16 kernel, with the exception of the CMD640 and RZ1000 which I don't compile in because I don't have the chips on my motherboard. I don't know what the SuSE 2.4.10-4GB kernel has set. I just have the kernel and not the sources and config files

# SCSI support # CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y CONFIG_SD_EXTRA_DEVS=40 CONFIG_BLK_DEV_SR=m CONFIG_SR_EXTRA_DEVS=2 CONFIG_CHR_DEV_SG=m # CONFIG_SCSI_DEBUG_QUEUES is not set # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set

Looks like mine in the self-compiled 2.4.16 kernel except that I also selected DEBUG_QUEUES, MULTI_LUN and CONSTANTS, but I had these selected back when I was using a self-compiled 2.4.6 kernel. It worked then. (I think 2.4.6 is the last self-compiled kernel I had that worked.) Again here, I can't say what SuSE has compiled in.

# # SCSI low-level drivers # [settings snipped]

This is different from mine since I have a different card. I only have the BusLogic card (CONFIG_SCSI_BUSLOGIC) selected in the low-level drivers. Do I need one of the others for ide-scsi? Don't think I ever did before. There is an option with the BusLogic source to deselect support for something called FlashPoint. I am going to rebuild the driver without the FlashPoint support and see if that works. Thanks, Sean -- Theo. Sean Schulze tschulze@nuthole.de "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker

On Sunday 27 January 2002 17:16, Anders Johansson wrote:

On Sunday 27 January 2002 16.39, Theo.Sean Schulze wrote:

...

Jan 27 15:58:07 dragoon modprobe: modprobe: Can't locate module block-major-11

Did ide-scsi.o load properly? You may need to modprobe it if the kernel autoloader doesn't identify it properly.

Here are the lines from /etc/modules.conf: # entries added per CD-Writer HOW_TO for ide-scsi options ide-cd ignore=hdb alias scd0 sr_mod # load ide-scsi before sg pre-install sg modprobe ide-scsi # load ide-scsi before sr_mod pre-install sr_mod modprobe ide-scsi # load ide-cd before ide-scsi pre-install ide-scsi modprobe ide-cd # end entries for CD-Writer HOW-TO ide-scsi.o won't load because id-cd.o is supposed to load before it. id-cd.o is not included in the modules installed with SuSE's 2.4.10-4GB on my machine.

...

Checking /etc/modules.conf, I find that block-major-11 is aliased to sr_mod, but when I use find to check for sr_mod.o under /lib/modules/2.4.10-4GB/kernel/drivers/scsi, I find that it isn't there. So, I checked the SuSE support database and found an article about IDE CD-R drive usage. This article says that ide-scsi support is compiled into the kernel (after SuSE Linux 7.0), and I can the line "hdb=scsi" in /etc/lilo.conf to get it to work.

hdb=ide-scsi, I believe is the correct usage.

Actually, that is what I have in my /etc/lilo.conf: append = "hdb=ide-scsi" This is the line given in the CD-Writing HOWTO, and it worked for me before. SuSE's support database and the help info shown under SCSI Emulation when using make menuconfig both show "hdx=scsi."

...

It also says to uncomment the line "alias scsi_hostadapter off" in /etc/modules.conf. I can't do that, because the line in my /etc/modules.conf is actually "alias scsi_hostadapter BusLogic." If I turn the scsi_hostadapter off, I will not be able to mount /kernel to which is mounted /dev/sda1 and which contains linux kernel source directories. (/usr/src/linux is currently a link to /kernel/linux-2.4.16; I moved my kernel sources off onto a 400MB scsi drive to save space on my root partition drive which was getting crowded.)

So, I could boot up with kernel 2.4.16 self-compiled from source, but when I try to do that I get the message:

/lib/modules/2.4.16/kernel/drivers/scsi/BusLogic.o unresolved symbol scsi_unregister_module /lib/modules/2.4.16/kernel/drivers/scsi/BusLogic.o unresolved symbol scsi_register /lib/modules/2.4.16/kernel/drivers/scsi/BusLogic.o unresolved symbol scsi_mark_host_reset /lib/modules/2.4.16/kernel/drivers/scsi/BusLogic.o unresolved symbol scsi_register_module /lib/modules/2.4.16/kernel/drivers/scsi/BusLogic.o unresolved symbol scsi_unregister

Looks like you forgot to include some part of the kernel scsi support.

You may have hit on the problem. I went back through the kernel configuration to figure out what it could be that I forgot, and I realized that I had configured both SCSI support and SCSI disk support as modules. The only module I was telling mk_initrd to load into the initrd file was the BusLogic.o. So, let me go back and recompile with both of the scsi options compiled in and see if that works. (Note: I would just add scsi_mod.o and sd_mod.o to the /etc/rc.config option for mk_initrd, but I am not certain how SuSE's stock kernel would behave if it was asked to load modules for support it already has compiled in. If this doesn't work, I will have to fall back on the SuSE stock kernel.)

...

kmod: failed to exec /sbin/modprobe -s -k block-major-22, errno=2 VFS: Cannot open root device "1601" or 16:01 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 16:01

Is hdc1 really your root? If so, check if you really compiled all modules you need to mount it (reiserfs, for instance) and that they really are included in the initrd, and that initrd is properly included in lilo.conf

Yep, I am pretty sure this is all correct. As I said, the SuSE kernel and my kernel live in the same directory on hdc1, so that can't be it. I think you were right on with the missing scsi support suggestion. I'll try that. Thanks, Sean -- Theo. Sean Schulze tschulze@nuthole.de "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker

Theo.Sean Schulze wrote:

This has taught me alot about how mk_initrd works, and I think it would be possible to put all these modules in the initrd. Does anyone know if the modules listed in /etc/rc.config's setting for INITRD_MODULES are loaded in the order they are listed?

From my experience, yes. I once put the driver for eth1 before the driver for eth0, and though both cards worked, it reversed which was which (ignored rc.config). YMMV. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871

On Monday 28 January 2002 15:47, Eddie Howson wrote:

This does sound long and rambling.

Yeah. Sorry. I started off with one problem and then realized what really had me bothered was that I couldn't get a self-compiled kernel to boot. Got that problem fixed now. Just need to figure out how SuSE's scripts set up isdn.

In the lilo.conf you need to add the line hdx=ide-scsi where x = b, c or d, depending on where your drive is installed.

This was never the problem, because this is in the CD-Writing-HOWTO.

Next if the ide-scsi module is not being loaded (you can check by running lsmod from the commandline as root) you can add

modprobe ide-scsi

to the /etc/init.d/boot.local file.

Well, this works, but you also need to make sure that you comment out or remove all of the lines you put into your /etc/modules.conf if you were originally following the HOWTO. I got curious about where you were finding all this, because I thought it should be in the documentation somewhere. I found SuSE's explanation in the 7.2 handbook. In there, however, it says to edit /etc/modules.conf so that it has this line in it: alias scsi_hostadapter ide-scsi

Finally, you may want to set up symbolic links e.g.

ln -sf /dev/scd0 /dev/cdrecorder

It shouldn't be anymore difficult than and shouldn't need you to compile or do anything else with the kernel. (I've literally just finished setting up the CDRW on a colleague's machine)

On the other hand, it shouldn't be so hard to integrate a self-compiled kernel into your system and get things to work.

Good luck

Thanks for the help. I wonder if I could set something up with "if else" statements to automate this so that I could compensate for the different requirements of a SuSE kernel and a self-compiled kernel. Cheer, Sean