Linux-Setup Digest #878, Volume #20 Wed, 21 Mar 01 05:13:07 EST
Contents:
Mouse problem on Compaq Presario 1230 ("Alex Ni")
Re: how do I get a service to start automatically? (preamp)
Problem upgrading from 2.2.14 to 2.4.2 (KCmaniac)
lilo on 20GB-HD (Klaus Reinhardt)
Re: lilo on 20GB-HD (David)
Symbios (LSI) 1010 Ultra160 SCSI ok with Linux? ([EMAIL PROTECTED])
Re: beginner: vfat mount problem after kernel 2.4.2 compilation ("Eric")
Re: Linux in NT/2000 domain ("Eric")
Reading and writing to a serial port (Kenneth Stephen)
Re: Strange lilo problem ("Eric")
Re: Linux <scream>Frustration!</scream> ("Eric")
Re: Problem upgrading from 2.2.14 to 2.4.2 (Dedicated to all Manson Fans)
ISDN dial-in using IPX?? (Mark Burger)
Re: Fetchmail from 1 mailbox to multiple recievers? (Michael Heiming)
Re: /dev/null is read-only ? ("Peter T. Breuer")
Re: Reading and writing to a serial port (Michael Heiming)
Re: Linux <scream>Frustration!</scream> ("Thumper")
Re: Problem upgrading from 2.2.14 to 2.4.2 (KCmaniac)
Problems with parallelport cd-writer ("Frank Enser")
Re: Adding memory... something I'm missing? ("Pavan")
Re: Problem upgrading from 2.2.14 to 2.4.2 ("Pavan")
----------------------------------------------------------------------------
From: "Alex Ni" <[EMAIL PROTECTED]>
Subject: Mouse problem on Compaq Presario 1230
Date: Wed, 21 Mar 2001 01:27:15 -0500
Hi,
I tried to install Redhat 7 on my Presario 1230 labtop (Compaq) and i did
get everything else but the mouse working. It seemed to me although the
mouse cursor did appear on the screen and can be dragged around basically as
desired from either the touchpad or the external one. But the weired thing
was that i could almost NEVER have it under control: all of a sudden when i
switch the direction in the mouse just jumped right back to where i got
started dragging it.
Someone plz lend me a hand on what the problem is?
Alex
------------------------------
From: preamp <[EMAIL PROTECTED]>
Subject: Re: how do I get a service to start automatically?
Crossposted-To: alt.os.linux.mandrake
Reply-To: [EMAIL PROTECTED]
Date: Wed, 21 Mar 2001 17:02:26 +1000
Anthony wrote:
> There's autoexec in dos & windows. Does linux (mandrake 7.2) have a
> similar file?
>
>
Yes, but autoexec.bat is not used to start services in a strict sense (as
in a Windows NT service). It does however start various programs.
If you just want to start a program automatically when you log in, you can
put stuff in .bash_profile (in your home directory).
For stuff that runs as the computer boots, read up on using the sysV init
levels.
------------------------------
From: KCmaniac <[EMAIL PROTECTED]>
Subject: Problem upgrading from 2.2.14 to 2.4.2
Date: Wed, 21 Mar 2001 02:09:33 -0500
Hoping somebody can help me with this.
I have configured and compiled the new kernal 2.4.2 with no apparent
problems.
I put new source files under /usr/src/linux and put the old source files
under /usr/src/linux-2.2.14.
I copied the new kernal image into /boot under the name vmlinuz-2.4.2.
The old kernal
is named vmlinuz-2.2.14 which I have kept in /boot. The new System.map
file is named
System.map-2.4.2 and the old is System.map-2.2.14. I insured that the
System.map
symbolic link in /boot is pointing to the new System.map-2.4.2.
I updated /etc/lilo.conf to reflect new kernal image which is to be
mounted as root=/dev/hda5
which is the same partition as the old kernal booted up in.
Upon reboot with new kernal a page of messages scrolls through but stops
with the last three
lines saying:
VFS: Cannot open root device "305" or 03:05
Please append a correct "root=" boot option
Kernal panic : VFS : Unable to mount root fs on 03:05
Boot process dies right there.
My only option was to use a rescue disk to boot with vmlinuz which boots
an old kernal
that at least allowed me to boot up to a valid or useable desktop.
There I was able to change
everything back to the 2.2.14 kernal. I reboot again and the linux
system boots just fine with that
kernal.
Can anybody tell me whats going on here?
When I compiled the 2.4.2 kernal its size was well under 640 MB(file
size shows around 600).
Is it possible that for some reason the new kernal does not like my disk
partitioning whereas the
old kernal is just fine with it??
How can I remedy this problem to use the new kernal?
Thanks anybody for any advice!
------------------------------
From: [EMAIL PROTECTED] (Klaus Reinhardt)
Subject: lilo on 20GB-HD
Date: Wed, 21 Mar 2001 07:46:18 GMT
Hi!
I want to install the lilo on a 20GB-HD. The fist partitions have
5GB for C: and D: for Win98. Now I want to install lilo to have
a 'perfect' password-access for win, too. But there is the
'known problem' of more than 1024 cylinders. The other option
is having some start-files on win-C:, but they could be deleted
by somebody ..
Is there another way?
Thanks in advance
K@Rdt
------------------------------
From: David <[EMAIL PROTECTED]>
Subject: Re: lilo on 20GB-HD
Date: Wed, 21 Mar 2001 07:59:00 GMT
Klaus Reinhardt wrote:
>
> Hi!
>
> I want to install the lilo on a 20GB-HD. The fist partitions have
> 5GB for C: and D: for Win98. Now I want to install lilo to have
> a 'perfect' password-access for win, too. But there is the
> 'known problem' of more than 1024 cylinders. The other option
> is having some start-files on win-C:, but they could be deleted
> by somebody ..
> Is there another way?
>
> Thanks in advance
> K@Rdt
You can get lilo-21.7 which should allow you to have /boot and /root
above the 1024th cylinder.
http://www.ibiblio.org/pub/Linux/system/boot/lilo/lilo-21.7.tar.gz
--
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
ID # 123538
Completed more W/U's than 99.120% of seti users. +/- 0.01%
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware
Subject: Symbios (LSI) 1010 Ultra160 SCSI ok with Linux?
Date: 21 Mar 2001 07:59:45 GMT
Hi,
Ladies and gentlemen, can someone tell me if the Ultra160 SCSI
chipset by Symbios/NCR (3C1010, used embedded in some high-end mother-
boards like the Tyan Thunder 2500) is compatible with current Linux, I
mean the current Linux kernels and if so which driver.
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: beginner: vfat mount problem after kernel 2.4.2 compilation
Date: Wed, 21 Mar 2001 09:09:53 +0100
> when I do a mount like this:
> mount /mnt/floppy or mount -t vfat /dev/fd0 /mnt/floppy I get
>
> mount: /dev/fd0 has wrong major or minor number
Are the major/minor numbers correct?
brw------- 1 a_user floppy 2, 0 May 5 1998 /dev/fd0
^^^^^^^
major,minor
Or are you missing some library? (libc/glibc)
> The led for the floppy drive blinks thus that means that he at least
> accesses it. I think that for some reason vfat isn't supported
> correctly.
You'd get a:
$> mount: fs type vfat not supported by kernel
if that was the case
> when I do cat /proc/filesystems, I see some filesystems but not vfat and
> msdos, do you know if I should see these filesystem types here?
It wil register once you used it.
> Same error when I try to mount a windows partition.
same command, so try `ldd /bin/mount`
Any libraries missing?
> The harddisk is an ATA66 harddisk and I have upgraded to the new kernel
> 2.4.2 because it supports my HPT366 controller on my mainboard.
> With the older kernel I was able to mount a windows floppy
> disk/partition but I could only boot my system from harddisk with the
> following parameters in /etc/lilo:
>
> append="ide2=0xa400, 0xa800 ide3=0xb000, 0xb400" which uses some low
> performance compatibility mode
I doubt this is causing troubles now.
It's just a driver.
Eric
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: Linux in NT/2000 domain
Date: Wed, 21 Mar 2001 09:30:34 +0100
> Normal nameserver is fine.
> My linux is also Redhat, pump works fine.
> While connecting to internet, no problem found.
> But it just cannot get intranet hosts by name (should be NetBios name)
nslookup hostname.domainname fails?
> except by IP.
> So, is there any way to solve it??
check what is in your /etc/resolv.conf
Are the nameservers listed that should resolv those intranet names?
Eric
> > > In my company, most computers in our domain are NT/2000 hosts.
> > > And Primary/Backup domain controller are 2000 server.
> > > All hosts' IP/DNS settings are from DHCP service.
> > > Now I set up a Linux host in same domain.
> > > It looks fine while connecting to Internet.
> > > But it cannot access other machines in local domain except by using
> > > explicit IP address.
> >
> > appears that the nameservers are not used.
> >
> > > Is there any way to solve this problem?
> > >
> >
> > Use them :-)
> > Are the nameservers not on a static IP address?
> > (that would be easy, put them in your /etc/resolv.conf)
> >
> > What dhcp client do you use
> > I use RedHat, which comes with pump, others may use dhcpcd
> > I never got dhcpcd working (on an NT domain too), pump works
> > without problems though.
> >
> > Eric
> >
> >
> >
> >
>
>
------------------------------
From: Kenneth Stephen <[EMAIL PROTECTED]>
Subject: Reading and writing to a serial port
Date: Wed, 21 Mar 2001 08:16:53 GMT
Hi,
I've got access to a Cisco switch that I can play around with, and
there is a serial port output on the box which is for console output. My
Linux box does have a serial port, but I havent got a clue as to what I
should do to hook up the switch to my Linux box so that I can use Linux
as the console for the switch. How can I solve this?
Thanks,
Kenneth
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: Strange lilo problem
Date: Wed, 21 Mar 2001 09:44:40 +0100
comp.os.linux.help doesn't exist anymore IIRC
> I'm having a problem installing lilo in the bootsector of my boot drive,
> and I was wondering if anyone's seen a problem like this before. The
> error I get is:
>
> Device 0x0800: Invalid partition table, 1st entry
> 3D address: 1/1/0 (32)
> Linear address: 32/1/0 (63)
>
>
> What does this mean?
It's in the User_Guide.ps (Which is on your system most likely)
You'll find that you could use a fix-table(?) directive.
I haven't read into this, so read before you try. There may be
serious penalty's if you use this.
> These are my hard drives:
Where did you get the values from?
What does `/sbin/fdisk -l /dev/sd[a-z]` show?
> Disk /dev/sda: 64 heads, 32 sectors, 35020 cylinders (windows, boot
> disk)
> Disk /dev/sdb: 64 heads, 32 sectors, 8748 cylinders (linux)
32 sectors?
Why does it use 32 sectors?
and why only 64 heads? the partition-table appearantly was created
with different values
> Disk /dev/sdc: 255 heads, 63 sectors, 1115 cylinders (old windows disk)
63 sectors, now that's more like it
> sdc used to be sda, and lilo installed perfectly fine then. I needed a
> larger
> windows drive, so I got a new one, set it up to be sda. I used windoze
> fdisk to create a fat32 partition and left a piece of the drive empty
> for linux stuff. If I run linux fdisk on sda, I get warnings that
> partitions do not end on cylinder boundaries, could this be confusing
> lilo?
Possibly, read the User_Guide
> Since these are scsi drives, I specified the bios mappings in the
> lilo.conf file:
>
> disk=/dev/sda
> bios=0x80
> disk=/dev/sdb
> bios=0x81
> disk=/dev/sdc
> bios=0x82
>
That's a good thing to do, but make sure they match the BIOS settings.
Otherwise it will only be a confusing thing, and lilo will fail on this too.
> Thanks in advance for any help, and please attach a reply by email as
> well.
To who?
I don't see your email address, and I'm not gooing to look for it.
Eric
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.pc-homebuilt
Subject: Re: Linux <scream>Frustration!</scream>
Date: Wed, 21 Mar 2001 09:52:49 +0100
> Here's my problem in a nutshell: I can't even get started with Linux.
> God knows I tried. I've jumped though flaming hoops and crawled through
> electrified mud to just get to the point where I can send a single piece
> of email via Linux without replacing all my components. I am still
> unsuccessful, and the problem is my hardware.
pretty pointless actions when you want to get a PC to work.
All you need to do is sacrifice a penguin to the linux god ;-)
> Supposedly Linux supports all that I've got, but it sure is hard to
> tell.
>
> My Specs:
>
> EPOX 7KXA mobo (slot A), Athlon 550, 256 MB PC-133 SDRAM, Jaton GeForce
> MX AGP vid, WD 15.3 G ATA 66 7200 RPM main drive (WinME), Maxtor 6.3 G
> ATA 66 slave drive (Linux), CompUSA 12X DVD ROM, Teac FDD, Komodo
> (Sceptre) 17" CRT, SMC PCI NIC, PCI Happauge WinTV, Dell ps/2 key,
> Logitech Marblemouse ps/2 trackball. All but the new vid card and the
> new HD worked before. I don't suspect the new HD - it's doing its job.
> Oh yeah, and a lovely Boca Tidalwave USB external HARDWARE, NOT WINMODEM
> 56K V.90 modem.
>
> I'm working with Mandrake 7.1. I have several other distros knocking
> around (long story), I've got VM Ware for Linux (a gift from an
> over-optimistic Linux advocate pal of mine) and the new kernel standing
> by on CD. I need the new kernel so I can theoretically get online with
> my USB modem.
>
> I won't bore you with all I went through just to get to the point where
> I am now. My problem now is that Linux doesn't like my wonderful new
> video card.
>
> When I was using my crummy old unstable Diamond s540 vid I had no
> trouble installing and booting into Linux. I had Linux on a partition
> on my main drive at that time. I could accept the display defaults at
> install time and get a gorgeous display. I plunked down some real money
> for a much better card, the Jaton GeForce MX, and under Windows this
> card is a dream. It solved a lot of instability problems I was having
> with the old card.
>
> I added the second drive specifically for Linux today. I was all
> excited about a fresh install. Unfortunately, when I installed Mandrake
> 7.1 today (the same CD that never failed before) I get as far as testing
> the display setup and I get a garbled image and the whole system locks.
> I know after a brief interval the display is supposed to flip back if I
> don't OK the setup I chose. That doesn't happen. It just locks, and I
> have to restart to escape.
>
> It's the vid card. It's that simple.
Then skip the X setup during the install/
Surely mandrake must have that option too.
You can always set it up afterwards
> Somebody please tell me: now what? I'm not putting back the old Diamond
> card. I'd rather give up on Linux completely, and I'm not going to do
> that either, although heaven knows by this time I've been given ample
> reason. Please don't tell me to RFM. I'm going to shoot the sadist who
> WFM, OK?
RTFM RTFM RTFM :-p
Really, take a look at www.xfree86.org and see wheter your card is
supported by the XFree86 you're using. You may need to upgrade it .
Eric
------------------------------
Date: Wed, 21 Mar 2001 10:08:42 +0100
From: Dedicated to all Manson Fans <[EMAIL PROTECTED]>
Subject: Re: Problem upgrading from 2.2.14 to 2.4.2
KCmaniac schrieb:
> Hoping somebody can help me with this.
>
> I have configured and compiled the new kernal 2.4.2 with no apparent
> problems.
>
> I put new source files under /usr/src/linux and put the old source files
> under /usr/src/linux-2.2.14.
>
> I copied the new kernal image into /boot under the name vmlinuz-2.4.2.
> The old kernal
> is named vmlinuz-2.2.14 which I have kept in /boot. The new System.map
> file is named
> System.map-2.4.2 and the old is System.map-2.2.14. I insured that the
> System.map
> symbolic link in /boot is pointing to the new System.map-2.4.2.
>
> I updated /etc/lilo.conf to reflect new kernal image which is to be
> mounted as root=/dev/hda5
> which is the same partition as the old kernal booted up in.
>
> Upon reboot with new kernal a page of messages scrolls through but stops
> with the last three
> lines saying:
>
> VFS: Cannot open root device "305" or 03:05
> Please append a correct "root=" boot option
> Kernal panic : VFS : Unable to mount root fs on 03:05
>
> Boot process dies right there.
>
> My only option was to use a rescue disk to boot with vmlinuz which boots
> an old kernal
> that at least allowed me to boot up to a valid or useable desktop.
> There I was able to change
> everything back to the 2.2.14 kernal. I reboot again and the linux
> system boots just fine with that
> kernal.
>
> Can anybody tell me whats going on here?
>
> When I compiled the 2.4.2 kernal its size was well under 640 MB(file
> size shows around 600).
>
> Is it possible that for some reason the new kernal does not like my disk
> partitioning whereas the
> old kernal is just fine with it??
>
> How can I remedy this problem to use the new kernal?
>
> Thanks anybody for any advice!
Are you sure you haven't compiled important drivers for your harddisks or
the support of the file system as modules?
------------------------------
From: Mark Burger <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: ISDN dial-in using IPX??
Date: Wed, 21 Mar 2001 10:08:57 +0100
Well, a friend of mine here in my town and me wanna play some old LAN
games that only run on IPX. So I wanna dial in with my Winblows machine
to his Linux computer (Suse 7.x) and get routed to his Winblows machine.
Where can I read something about it? All I found referred to TCP/IP. TIA!
--
"Alright, here is the plan - ..."
"Ugh uuuugh ... ugh ugh ugh"
"What kind of moronic plan is that?"
------------------------------
Date: Wed, 21 Mar 2001 10:13:06 +0100
From: Michael Heiming <[EMAIL PROTECTED]>
Subject: Re: Fetchmail from 1 mailbox to multiple recievers?
Liquor wrote:
>
> I'm sure there are many ways to do it :)
>
> I have a gateway/firewall machine on a dial-up line, and
> it has a default (RedHat 6.2) installation of sendmail (not
> running as a daemon, just invoked locally by mail) and
> imap server that at the moment is just providing shared mail
> folders for multiple clients.
>
> I know I can just use fetchmail to bring mail from a single
> server account to a single user account accessible by imap -
> but I want to sort mailing-list traffic into a separate
> inbox. I can distinguish it by the sender address, the
> reply-to address, or even by the contents of the subject line.
>
> Does anybody have any suggestions for the easiest way to
> accomplish this? or even pointers for what part
> of TFM I should R?
>
> TIA,
> --
> Liquor
Hello,
you could use procmail, if it's setup on your box and is as mostly sendmails LDA
(grep Mlocal /etc/sendmail.cf will show)
Try something like this in your homedir as .procmailrc (You may have to adjust
some PATH...)
SHELL=/bin/sh
SENDMAIL=/usr/sbin/sendmail
MAILDIR=/Path/to_your_IMAP_Maildir/$USER
VERBOSE=ON
LOGABSTRACT=all
LOGFILE=/home/$USER/proclog
FORMAIL=/usr/bin/formail
DATE=/bin/date
CAT=/bin/cat
* !^X-Loop: your_username@yourdomain
:0:
* ^Subject:.*Your_choice*
$MAILDIR/Folder_you_want_it
:0:
* ^[EMAIL PROTECTED]
$MAILDIR/php
Add more if you like. You may want to lower logging in case everything is working
fine.
apropos procmail
Shows you all man pages on this topic, read them to learn more about procmail.
Good luck
Michael Heiming
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat,comp.os.linux.questions,comp.os.linux.networking
Subject: Re: /dev/null is read-only ?
Date: Wed, 21 Mar 2001 09:57:17 +0100
In comp.os.linux.setup Christopher H <[EMAIL PROTECTED]> wrote:
> I get the following error:
> MAKEDEV: urandom is a read-only filesystem
It is? So repair it! Run /sbin/fsck on it, quickly! When you are done,
remount it readwrite (mount -wo remount /).
Peter
------------------------------
Date: Wed, 21 Mar 2001 10:17:35 +0100
From: Michael Heiming <[EMAIL PROTECTED]>
Subject: Re: Reading and writing to a serial port
Kenneth Stephen wrote:
>
> Hi,
>
> I've got access to a Cisco switch that I can play around with, and
> there is a serial port output on the box which is for console output. My
> Linux box does have a serial port, but I havent got a clue as to what I
> should do to hook up the switch to my Linux box so that I can use Linux
> as the console for the switch. How can I solve this?
I would check the manual of your cisco, it should explain what you can do and how
to connect
your cisco through serial, may be there is some kind of terminal waiting...
Good luck
Michael Heiming
------------------------------
From: "Thumper" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.pc-homebuilt
Subject: Re: Linux <scream>Frustration!</scream>
Date: Wed, 21 Mar 2001 09:15:35 GMT
Well you need to read......just kidding..:)
Actually here are 2 things you can try...
1. Grab the latest Nvidia (GeForce MX is Nvidia chipset)linux drivers from
their site at the following website
http://www.nvidia.com/Products/Drivers.nsf/Linux.html
and/or
2. Upgrade to XFree86 4.0.2 at
http://www.xfree86.org/
specific coverage for your chipset is here
http://www.xfree86.org/current/Status22.html#22
Hope this helps.
--
Thumper
Kill da munge to reply by email.
Registered Linux user #209449 - Machine registration #97328
"Laura Goodwin" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Here's my problem in a nutshell: I can't even get started with Linux.
> God knows I tried. I've jumped though flaming hoops and crawled through
> electrified mud to just get to the point where I can send a single piece
> of email via Linux without replacing all my components. I am still
> unsuccessful, and the problem is my hardware.
>
> Supposedly Linux supports all that I've got, but it sure is hard to
> tell.
>
> My Specs:
>
> EPOX 7KXA mobo (slot A), Athlon 550, 256 MB PC-133 SDRAM, Jaton GeForce
> MX AGP vid, WD 15.3 G ATA 66 7200 RPM main drive (WinME), Maxtor 6.3 G
> ATA 66 slave drive (Linux), CompUSA 12X DVD ROM, Teac FDD, Komodo
> (Sceptre) 17" CRT, SMC PCI NIC, PCI Happauge WinTV, Dell ps/2 key,
> Logitech Marblemouse ps/2 trackball. All but the new vid card and the
> new HD worked before. I don't suspect the new HD - it's doing its job.
> Oh yeah, and a lovely Boca Tidalwave USB external HARDWARE, NOT WINMODEM
> 56K V.90 modem.
>
> I'm working with Mandrake 7.1. I have several other distros knocking
> around (long story), I've got VM Ware for Linux (a gift from an
> over-optimistic Linux advocate pal of mine) and the new kernel standing
> by on CD. I need the new kernel so I can theoretically get online with
> my USB modem.
>
> I won't bore you with all I went through just to get to the point where
> I am now. My problem now is that Linux doesn't like my wonderful new
> video card.
>
> When I was using my crummy old unstable Diamond s540 vid I had no
> trouble installing and booting into Linux. I had Linux on a partition
> on my main drive at that time. I could accept the display defaults at
> install time and get a gorgeous display. I plunked down some real money
> for a much better card, the Jaton GeForce MX, and under Windows this
> card is a dream. It solved a lot of instability problems I was having
> with the old card.
>
> I added the second drive specifically for Linux today. I was all
> excited about a fresh install. Unfortunately, when I installed Mandrake
> 7.1 today (the same CD that never failed before) I get as far as testing
> the display setup and I get a garbled image and the whole system locks.
> I know after a brief interval the display is supposed to flip back if I
> don't OK the setup I chose. That doesn't happen. It just locks, and I
> have to restart to escape.
>
> It's the vid card. It's that simple.
>
> Somebody please tell me: now what? I'm not putting back the old Diamond
> card. I'd rather give up on Linux completely, and I'm not going to do
> that either, although heaven knows by this time I've been given ample
> reason. Please don't tell me to RFM. I'm going to shoot the sadist who
> WFM, OK?
>
>
> Laura Goodwin
------------------------------
From: KCmaniac <[EMAIL PROTECTED]>
Subject: Re: Problem upgrading from 2.2.14 to 2.4.2
Date: Wed, 21 Mar 2001 04:33:16 -0500
Dedicated to all Manson Fans wrote:
> KCmaniac schrieb:
>
> > Hoping somebody can help me with this.
> >
> > I have configured and compiled the new kernal 2.4.2 with no apparent
> > problems.
> >
> > I put new source files under /usr/src/linux and put the old source files
> > under /usr/src/linux-2.2.14.
> >
> > I copied the new kernal image into /boot under the name vmlinuz-2.4.2.
> > The old kernal
> > is named vmlinuz-2.2.14 which I have kept in /boot. The new System.map
> > file is named
> > System.map-2.4.2 and the old is System.map-2.2.14. I insured that the
> > System.map
> > symbolic link in /boot is pointing to the new System.map-2.4.2.
> >
> > I updated /etc/lilo.conf to reflect new kernal image which is to be
> > mounted as root=/dev/hda5
> > which is the same partition as the old kernal booted up in.
> >
> > Upon reboot with new kernal a page of messages scrolls through but stops
> > with the last three
> > lines saying:
> >
> > VFS: Cannot open root device "305" or 03:05
> > Please append a correct "root=" boot option
> > Kernal panic : VFS : Unable to mount root fs on 03:05
> >
> > Boot process dies right there.
> >
> > My only option was to use a rescue disk to boot with vmlinuz which boots
> > an old kernal
> > that at least allowed me to boot up to a valid or useable desktop.
> > There I was able to change
> > everything back to the 2.2.14 kernal. I reboot again and the linux
> > system boots just fine with that
> > kernal.
> >
> > Can anybody tell me whats going on here?
> >
> > When I compiled the 2.4.2 kernal its size was well under 640 MB(file
> > size shows around 600).
> >
> > Is it possible that for some reason the new kernal does not like my disk
> > partitioning whereas the
> > old kernal is just fine with it??
> >
> > How can I remedy this problem to use the new kernal?
> >
> > Thanks anybody for any advice!
>
> Are you sure you haven't compiled important drivers for your harddisks or
> the support of the file system as modules?
I'll check that again but I'm pretty sure I didn't. But as soon as I say that
I'll probably find otherwise.
Thanks for the suggestion.
------------------------------
From: "Frank Enser" <[EMAIL PROTECTED]>
Subject: Problems with parallelport cd-writer
Date: Wed, 21 Mar 2001 10:36:23 +0100
Hi,
I've got some problem mit my parallelport cd-writer and using cdrecord 1.9.
(It is a HP 7200 CD-Writer connected to the parallel port). By the way, I'm
using SuSE Linux 7.1 with the 2.4.2 kernel.
I've loaded all necessary modules:
> lsmod
ide-scsi 7792 0
pg 6096 0 (autoclean)
epat 6208 1
paride 3808 1 (autoclean) [pg epat]
sg 21056 0 (autoclean) (unused)
scsi_mod 83104 2 (autoclean) [ide-scsi sg]
parport_pc 13280 2 (autoclean)
lp 5072 1 (autoclean)
parport 24320 2 (autoclean) [paride parport_pc lp]
usb-uhci 21728 0 (unused)
3c59x 22848 1 (autoclean)
In the kernel messages entries like
kernel: paride: version 1.05 installed
kernel: paride: epat registered as protocol 0
kernel: pg: pg version 1.02, major 97
kernel: pg0: Sharing parport0 at 0x378
kernel: pg0: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 2 (8-bit), delay
1
kernel: pg0: HP CD-Writer+ 7200, slave
appear, so I think the device is properly installed and recognized.
Then I try to find the device by rescanning the SCSI bus, nothing is found.
> rescan-scsi-bus.sh
Host adapter 0 (ide-scsi) found.
0 new device(s) found.
0 device(s) removed.
And when I try to start cdrecord, I get a nice message like:
> cdrecord -scanbus -debug
dev: (NULL POINTER) speed: -1 fs: -1
Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 J�rg Schilling
TOC Type: 1 = CD-ROM
PP Bus: -2
Bus: 0 cookie: FFFFFFFF
file (0,0,0): 3
Bus: 1 cookie: FFFFFFFF
Bus: 2 cookie: FFFFFFFF
Bus: 3 cookie: FFFFFFFF
Bus: 4 cookie: FFFFFFFF
Bus: 5 cookie: FFFFFFFF
Bus: 6 cookie: FFFFFFFF
Bus: 7 cookie: FFFFFFFF
Bus: 8 cookie: FFFFFFFF
Bus: 9 cookie: FFFFFFFF
Bus: 10 cookie: FFFFFFFF
Bus: 11 cookie: FFFFFFFF
Bus: 12 cookie: FFFFFFFF
Bus: 13 cookie: FFFFFFFF
Bus: 14 cookie: FFFFFFFF
Bus: 15 cookie: FFFFFFFF
Using libscg version 'schily-0.1'
SCSI buffer size: 32768
scsi_getbuf: 32768 bytes
scsibus0:
ioctl ret: -1
cdrecord: Inappropriate ioctl for device. Cannot send SCSI cmd via ioctl
So can anyone help me. (I hope someone can....)
Frank
------------------------------
From: "Pavan" <[EMAIL PROTECTED]>
Subject: Re: Adding memory... something I'm missing?
Date: Wed, 21 Mar 2001 15:07:49 +0530
.
>
> Do I need to do something special when adding memory?
>
When I added new memory, I had problems with windows. Linux worked
just fine. The problem is with mixing the old and new memories. Each
independently worked just fine. So I later put just new memory.
-Pavan
------------------------------
From: "Pavan" <[EMAIL PROTECTED]>
Subject: Re: Problem upgrading from 2.2.14 to 2.4.2
Date: Wed, 21 Mar 2001 15:15:08 +0530
>
> VFS: Cannot open root device "305" or 03:05
> Please append a correct "root=" boot option
> Kernal panic : VFS : Unable to mount root fs on 03:05
>
May I ask if you have compiled second extended filesystem support into
the new kernel?
Also instead of replacing the old kernel in lilo.conf, it is always
better to create a new entry so that the old kernel can be booted even
if the new one has problems.
-Pavan
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************