IDE master to slave conversion

2002-09-22 Thread Neal Pollock



I'm changing the position of my IDE drives and 
subsequently need to set my debian disk as a slave. What configuration 
files do i need to edit to ensure a clean boot with all services running 
properly?  ie. root=/dev/hda6 becomes root=/dev/hdb6 in 
lilo.conf.
 
cheers.


eth0 problem after kernal package upgrade

2002-09-26 Thread Neal Pollock

i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via
dselect.  Unfortunately when I boot the new kernel i cannot establish an
internet connection.  Am I correct in assuming that i need to to check:

a) eth0 is properly configured
b) dhcpclient obtained an IP

inorder to troubleshoot this problem.  i thought the new kernel would run
all my old services and leave my system configuration untouched. what's
happening?

neal.


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




Re: eth0 problem after kernal package upgrade

2002-09-26 Thread Neal Pollock

Thanks for the repsonse, here's my details:

http://members.rogers.com/npollock1/sysinfo.txt

Neal.

- Original Message -
From: "nate" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 2:46 PM
Subject: Re: eth0 problem after kernal package upgrade


> Neal Pollock said:
> > i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image
> > via dselect.  Unfortunately when I boot the new kernel i cannot
establish
> > an internet connection.  Am I correct in assuming that i need to to
> > check:
> >
> > a) eth0 is properly configured
> > b) dhcpclient obtained an IP
> >
> > inorder to troubleshoot this problem.  i thought the new kernel would
run
> > all my old services and leave my system configuration untouched. what's
> > happening?
>
> do you have an eth0 interface? maybe the new kernel doesn't have a working
> driver for your NIC(unlikely but it is possible). what kind of NIC?
>
> 2.2.x to 2.4.x is a MASSIVE upgrade so it's not unusual to have such a
> problem IMO.
>
> so questions:
>
> what NIC chipset
> what driver are you using
> whats the output of 'lsmod'
> whats the output of 'ifconfig -a'
> whats the output of 'route -n'
> whats the output of 'dmesg'
>
> preferrably if you can post this on a website and post a link to
> the site rather then email everything that would be best, save some
> people some bandwidth.
>
> nate
>
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>


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




Re: eth0 problem after kernal package upgrade

2002-09-27 Thread Neal Pollock

Thanks Shayamal.  I have the following lines from 'dmesg' on 2.2.20 kernel:

"eth0: Macronix 98715 PMAC rev 37 at 0xd400, 00:80:C6:EA:C0:69, IRQ 4
eth0:  EEPROM default media type 10baseT.
via-rhine.c:v1.08b-LK1.0.1 12/14/2000"

How can I discern the name of the driver module for 2.4.18 from this?

Neal.
- Original Message -
From: "Shyamal Prasad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 9:22 AM
Subject: Re: eth0 problem after kernal package upgrade


> "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
>
> Neal> Thanks for the repsonse, here's my details:
> Neal> http://members.rogers.com/npollock1/sysinfo.txt
>
> Neal,
>
> I think the only thing you missed there is the kind of NIC you
> have. If you don't know this look in the output of 'lspci' for a
> hint. For example, on my machine I see this line in the lspci output:
>
> "00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet
> Controller (rev 70)"
>
> which gives me a good clue that this is supported by the via-rhine
> driver. If you can't guess what the driver is, try booting into your
> 2.2.x kernel and look in the output of dmesg for a line starting with
> "eth0'. In my case I might have seen something like this:
>
> "eth0: VIA VT6102 Rhine-II at 0xe400, 00:50:2c:03:26:a8, IRQ 11."
>
> which really does not offer a clue as to the driver name, but who
> knows, you might get luckier. If you don't have a PCI NIC this won't
> work (and it's been far too long since I messed with ISA cards to
> remember how to help you!).
>
> Now do the following as root:
>
> modprobe via-rhine #use the appropriate NIC driver module name
> ifconfig eth0 #to see if it works now
> ifdown eth0 #might fail, no worries
> ifup eth0
>
> If you have /etc/network/interfaces set up correctly from earlier this
> should fix your problem. Then add a line to /etc/modules containing
> the name of your driver so the next time you boot things are okay.
>
> Cheers!
> Shyamal
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>


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




1Re: eth0 problem after kernal package upgrade

2002-09-27 Thread Neal Pollock

a... I found the driver in /lib/modules/2.4.18-k7/kernel/drivers/net/

- Original Message -
From: "Neal Pollock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Shyamal Prasad"
<[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 10:19 PM
Subject: Re: eth0 problem after kernal package upgrade


> Thanks Shayamal.  I have the following lines from 'dmesg' on 2.2.20
kernel:
>
> "eth0: Macronix 98715 PMAC rev 37 at 0xd400, 00:80:C6:EA:C0:69, IRQ 4
> eth0:  EEPROM default media type 10baseT.
> via-rhine.c:v1.08b-LK1.0.1 12/14/2000"
>
> How can I discern the name of the driver module for 2.4.18 from this?
>
> Neal.
> - Original Message -
> From: "Shyamal Prasad" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, September 27, 2002 9:22 AM
> Subject: Re: eth0 problem after kernal package upgrade
>
>
> > "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
> >
> > Neal> Thanks for the repsonse, here's my details:
> > Neal> http://members.rogers.com/npollock1/sysinfo.txt
> >
> > Neal,
> >
> > I think the only thing you missed there is the kind of NIC you
> > have. If you don't know this look in the output of 'lspci' for a
> > hint. For example, on my machine I see this line in the lspci output:
> >
> > "00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet
> > Controller (rev 70)"
> >
> > which gives me a good clue that this is supported by the via-rhine
> > driver. If you can't guess what the driver is, try booting into your
> > 2.2.x kernel and look in the output of dmesg for a line starting with
> > "eth0'. In my case I might have seen something like this:
> >
> > "eth0: VIA VT6102 Rhine-II at 0xe400, 00:50:2c:03:26:a8, IRQ 11."
> >
> > which really does not offer a clue as to the driver name, but who
> > knows, you might get luckier. If you don't have a PCI NIC this won't
> > work (and it's been far too long since I messed with ISA cards to
> > remember how to help you!).
> >
> > Now do the following as root:
> >
> > modprobe via-rhine #use the appropriate NIC driver module name
> > ifconfig eth0 #to see if it works now
> > ifdown eth0 #might fail, no worries
> > ifup eth0
> >
> > If you have /etc/network/interfaces set up correctly from earlier this
> > should fix your problem. Then add a line to /etc/modules containing
> > the name of your driver so the next time you boot things are okay.
> >
> > Cheers!
> > Shyamal
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> >
> >
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>


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




Re: 1Re: eth0 problem after kernal package upgrade

2002-09-27 Thread Neal Pollock

tulip worked beautifully.  I apoligize for not mentioning the driver in my
previous post.

Shyamal you can read my mind ;)

- Original Message -
From: "Shyamal Prasad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Neal Pollock" <[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 11:20 PM
Subject: Re: 1Re: eth0 problem after kernal package upgrade


> "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
>
> Neal> a... I found the driver in
> Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/
>
> >>  "eth0: Macronix 98715 PMAC rev 37 at 0xd400,
> >> 00:80:C6:EA:C0:69, IRQ 4 eth0: EEPROM default media type
> >> 10baseT.  via-rhine.c:v1.08b-LK1.0.1 12/14/2000"
> >>
> >> How can I discern the name of the driver module for 2.4.18 from
> >> this?
>
> Which one? Like I said in my earlier post a few minutes ago, I'm
> leaning towards the tulip driver. I believe the via-rhine driver is
> just printing an empty line (it used to be a very verbose driver a
> while back), and the "eth0" line is actually coming from the "real"
> driver (which I'm *guessing* is tulip).
>
> If you do get it work, please let us know! Improve the collective
> knowledge base and all that.;-)
>
> Cheers!
> Shyamal
>


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




cramfs: wrong magic, kernel panic

2002-09-28 Thread Neal Pollock

I was experimenting with different video modes and I can no longer boot my
system.  I was passing different modes at the prompt, and used 'scan' from
the video mode menu.  I chose a mode and couldn't see anything so I gave the
machine a clt-alt-del.  Now I can't boot either of my two kernels (2.2.20 &
2.4.18) from lilo, I get the following messages:

(2.4.18)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: [PTBL] [4866/255/63] p1 p3 < p5 p6 p7 >
 /dev/ide/host0/bus0/target0/lun0: [PTBL] [1046/255/63] p1 p2 p3 p4 < p5 p6
p7 >
cramfs: wrong magic
Kernel panic: VFS: Unable to mount root fs on 3:46

(2.2.20)
[MS-DOS FS Rel. 12, FAT 12, Check=n, conv=b, uid=0, gid=0, umask=022, bmap]
 [me=0x0, cs=0, #f=0, fs=0, f1=0, ds=0, de=0, data =0, se=0, ts=0, ls=0,
rc=0, fc=42949672
Transaction block size = 512
Invalid session number or type of track
Kernel panic: VFS: Unable to mount root fs on 3:46

If I use the debian boot disk I get this messsge:

request_module[nls_cp437]: Root fd not mounted
Unable to load NLS charset cp437
VFS: Mounted root (msdos filesystem) readonly.
Freeing unused kernel memory: 72k freed
Warning: unable to open an initial console.
Kernel panic: No init found.  Try passing init= option to kernel.

I'm not sure why there's mention of 'MS-DOS FS' since all of my dos
partitions are on /dev/hda and linux boots from /dev/hdb. Could I have reset
the computer while lilo was writing to the bootsector?

Neal


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




Re: cramfs: wrong magic, kernel panic

2002-09-29 Thread Neal Pollock

Let me clarify.

- Original Message -
From: "Eduard Bloch" <[EMAIL PROTECTED]>
To: "Neal Pollock" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, September 29, 2002 6:06 AM
Subject: Re: cramfs: wrong magic, kernel panic

> > Partition check:
> >  /dev/ide/host0/bus0/target0/lun0: [PTBL] [4866/255/63] p1 p3 < p5 p6 p7
>
> >  /dev/ide/host0/bus0/target0/lun0: [PTBL] [1046/255/63] p1 p2 p3 p4 < p5
p6
> > p7 >
>
> What is that? Same disk with different partition tables? Burried your
> part. table somehow?

The first disk ( p1 p3 ) is hda and contains only fat32 partitions
strictly for win2k.
The second disk (p1 p2 p3 p4 < p5 p6 p7>) is hdb and contains my ext2, ext3
and swap partitions for debian.

> > cramfs: wrong magic
>
> That's the autoprobing. Seems like your filesystem has not been
> recognized.
>
> > Kernel panic: VFS: Unable to mount root fs on 3:46
>
> What is that? What does the kernel look on "/dev/hda46"? Try with
> root=/dev/ide/host0/bus0/target0/lun0/part

Tried it.  Got the following:
'Kernel panic: I have no root and I want to scream' ???

> > request_module[nls_cp437]: Root fd not mounted
> > Unable to load NLS charset cp437
> > VFS: Mounted root (msdos filesystem) readonly.
>
> Huch, what is 3:46?
>
> > Freeing unused kernel memory: 72k freed
> > Warning: unable to open an initial console.
> > Kernel panic: No init found.  Try passing init= option to kernel.
>
> It has mounted the wrong partition. Get a rescue system (you can use the
> install disk as a such one, second console) to make researches.
>
> > partitions are on /dev/hda and linux boots from /dev/hdb. Could I have
reset
> > the computer while lilo was writing to the bootsector?
>
> YOU must know this.

I couldn't see anything as my screen was blank.

> Gruss/Regards,
> Eduard.
> --
> 'Und dann muß man den Computer herunterladen, sonst stürzt er ab.'
>  (Harald Schmidt)
>


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




Re: Defeting Crappy Bios

2002-09-29 Thread Neal Pollock

The easiest way to get around this is to boot from a windows diskette and
flash a more liberal bios.  You can get an updated bios from compaq directly
(it was patched for y2k), although I'm unsure wether this bios will solve
your problem.

http://www29.compaq.com/falco/sp_result.asp?Model=2722&Os=0

HTH,

Neal.

- Original Message -
From: "TooMany Mirrors" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 30, 2002 1:15 AM
Subject: Defeting Crappy Bios


> I have a compaq computer I got for $30.00 and though a good price, has a
> really awful bios feature that not only only lets me boot to a floppy it
> won't boot to anything but a windows boot disk. I hostly can't explain it,
> but that is the state of things, so don't ask :)
> So my question is if there is a way to boot to a windows floppy, I have a
> win98 disk available so it's idea for me, and still install Linux.  I'm
also
> concered about being able to boot linux once it's install (if it's
installed
> :) )
> Thanks for any tips.
> By the way it's a Compaq Presario 4714 with a Pentium 1 and 24MB mem so on
> an so forth.
>
>
>
> _
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>


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




Text console flicker during kernel load

2002-10-01 Thread Neal Pollock

I've convinced my brother to try Debian and just set it up on his PC.
Unfortunately, from the time that lilo passes control onto the kernel until
the display manager login appears, the screen flickers on and off
continuously.  It stays on for about 1/3 of sec and then goes off for a 1/3
of a sec.  The video adapter is an ATI RagePro 3D AGP 1/2x.

X works fine, and I have 'vga=ask' in my lilo.conf, but regardless of what
display setting I choose the screen flickers.  I'm running 2.4.18 bf24
kernel, anyone know of a fix?

Neal.


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




Re: Text console flicker during kernel load

2002-10-02 Thread Neal Pollock

Thanks, I'd like to disable the framebuffer.  Whats the easiest way to do so
with a kernel recompile?

Neal.
- Original Message -
From: "Robert Ian Smit" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 02, 2002 5:56 AM
Subject: Re: Text console flicker during kernel load


> * Neal Pollock <[EMAIL PROTECTED]> [02-10-2002 06:35]:
> > I've convinced my brother to try Debian and just set it up on his PC.
> > Unfortunately, from the time that lilo passes control onto the kernel
until
> > the display manager login appears, the screen flickers on and off
> > continuously.  It stays on for about 1/3 of sec and then goes off for a
1/3
> > of a sec.  The video adapter is an ATI RagePro 3D AGP 1/2x.
>
> If you are able to compile a kernel, make one without framebuffer
> support for the console.
>
> Otherwise you'll have to look again at what options you are passing
> to the kernel.
>
> On a related note, why use framebuffer at all? It's always the first
> thing I unset, in case I forget later on. Am I missing something?
> (besides tux in the boot screen).
>
> Bob
>
>
> --
> To  UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>


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




Re: Text console flicker during kernel load

2002-10-02 Thread Neal Pollock

my bad...*without* a kernel recompile?
- Original Message -
From: "Neal Pollock" <[EMAIL PROTECTED]>
To: "Robert Ian Smit" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 02, 2002 10:21 PM
Subject: Re: Text console flicker during kernel load


> Thanks, I'd like to disable the framebuffer.  Whats the easiest way to do
so
> with a kernel recompile?
>
> Neal.
> - Original Message -
> From: "Robert Ian Smit" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, October 02, 2002 5:56 AM
> Subject: Re: Text console flicker during kernel load
>
>
> > * Neal Pollock <[EMAIL PROTECTED]> [02-10-2002 06:35]:
> > > I've convinced my brother to try Debian and just set it up on his PC.
> > > Unfortunately, from the time that lilo passes control onto the kernel
> until
> > > the display manager login appears, the screen flickers on and off
> > > continuously.  It stays on for about 1/3 of sec and then goes off for
a
> 1/3
> > > of a sec.  The video adapter is an ATI RagePro 3D AGP 1/2x.
> >
> > If you are able to compile a kernel, make one without framebuffer
> > support for the console.
> >
> > Otherwise you'll have to look again at what options you are passing
> > to the kernel.
> >
> > On a related note, why use framebuffer at all? It's always the first
> > thing I unset, in case I forget later on. Am I missing something?
> > (besides tux in the boot screen).
> >
> > Bob
> >
> >
> > --
> > To  UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> >
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>


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