Re: kernel-2.2.17

[Chris Tillman]

On Fri, Feb 08, 2002 at 02:19:53PM +0200, Ariel Tankus wrote:
> 
>I installed woody about a month ago (boot-floppies 3.0.18).
> Today I was trying to compile a frame grabber driver demanding the
> kernel sources.  I found a few things:
> 1.  The kernel on my machine is 2.2.17.

Did you upgrade from a potato system? The kernel is not upgraded if
you upgrade using apt-get, unless you specifically apt-get a kernel
package. Even then, it's not enabled by default.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: kernel-2.2.17

[David Kimdon]

Hi,

> kernel sources.  I found a few things:
> 1.  The kernel on my machine is 2.2.17.
> 2.  The kernel sources are not installed by default (This by itself is OK,
> but the surprise is:)
> 3.  There is no kernel source package for 2.2.17 on woody!

That's okay, 3.0.18 boot-floppies were created in December, woody now uses 2.2.20.


> Some more weird stuff:
> kernel-patch-2.2.17-pc9800
> kernel-patch-2.2.17-vm-global
> exist in woody, even though there is no kernel source
> for 2.2.17 to patch against ...
>
That may be a bug.  If the patches are not longer relevent they should
be removed.  If they don't apply to recent kernels they should be
either updated or removed.  In any case the bugs would be filed
against the kernel-patch packages in question.

-David


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

kernel-2.2.17

[Ariel Tankus]

   I installed woody about a month ago (boot-floppies 3.0.18).
Today I was trying to compile a frame grabber driver demanding the
kernel sources.  I found a few things:
1.  The kernel on my machine is 2.2.17.
2.  The kernel sources are not installed by default (This by itself is OK,
but the surprise is:)
3.  There is no kernel source package for 2.2.17 on woody!

Did I miss anything here?

Some more weird stuff:
kernel-patch-2.2.17-pc9800
kernel-patch-2.2.17-vm-global
exist in woody, even though there is no kernel source
for 2.2.17 to patch against ...


-- Ariel.

---
Ariel Tankus
School of Computer Science
Tel-Aviv University
[EMAIL PROTECTED]


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

Re: kernel 2.2.17 boot disk prob!

[Adam Di Carlo]

Sven Burgener <[EMAIL PROTECTED]> writes:
> Forgive me for sending this mail in a cross-posting fashion, but I
> really need some help here. This is what I posted previously to
> debian-user:
> 
> Thanks in advance for any replies!

Well, you could check whether the rescue disk works and thereby
confirm whether it's a partitioning or lilo problem vs a kernel
problem.

You didn't include partition information.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


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

Re: kernel 2.2.17 boot disk prob! (HELP!)

[Pann McCuaig]

On Wed, Jul 05, 2000 at 00:12, Sven Burgener wrote:
> On Tue, Jul 04, 2000 at 02:41:40PM -0700, Pann McCuaig wrote:
> > > What I'm looking for is a way of creating a boot disk like the one I
> > > created when installing debian initially.
> 
> > Do you still have that disk? There is a file on there named linux.
> > Delete it and replace it with a copy of /boot/vmlinuz-2.2.17.
> 
> I did that and it just did the job. :) Thanks!
> At first, it complained about missing dependencies but on the next
> bootstrap this was fine.
> 
> How often can this be repeated? I mean, do any other files on there need
> replacing sometime?

Install the syslinux package if it's not already installed and RTFM.  :-)

$ dpkg -l | grep syslinux
ii  syslinux   1.42-2 Bootloader for Linux/i386 using MS-DOS flopp

$ ls -l /usr/doc/syslinux/
total 18
-rw-r--r--1 root root 1215 Dec  5  1998 README
-rw-r--r--1 root root  342 Dec  5  1998 TODO
-rw-r--r--1 root root 1986 Dec 17  1998 changelog.Debian.gz
-rw-r--r--1 root root 2780 Dec  5  1998 changelog.gz
-rw-r--r--1 root root 1327 Dec 17  1998 copyright
-rw-r--r--1 root root 7635 Dec  5  1998 syslinux.doc.gz

(this is from my slink++ system)

Luck,
Pann
-- 
geek by nature, Linux by choice L I N U X   .~.
The Choice  /V\
http://www.ourmanpann.com/linux/ of a GNU  /( )\
Generation ^^-^^


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

Re: kernel 2.2.17 boot disk prob! (HELP!)

[Sven Burgener]

On Tue, Jul 04, 2000 at 02:41:40PM -0700, Pann McCuaig wrote:
> > What I'm looking for is a way of creating a boot disk like the one I
> > created when installing debian initially.

> Do you still have that disk? There is a file on there named linux.
> Delete it and replace it with a copy of /boot/vmlinuz-2.2.17.

I did that and it just did the job. :) Thanks!
At first, it complained about missing dependencies but on the next
bootstrap this was fine.

How often can this be repeated? I mean, do any other files on there need
replacing sometime?

On it now is the following:

# file /floppy/*
/floppy/ldlinux.sys:  data
/floppy/linux:Linux kernel x86 boot executable bzImage, version 2.2.17 
(herbert@arnor) #1 Sun J, RO-rootFS, root_dev=0x302, Normal VGA
/floppy/message.txt:  English text
/floppy/syslinux.cfg: ASCII text

And mount says:

# mount
/dev/hdb3 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hdb1 on /boot type ext2 (rw)
/dev/fd0 on /floppy type msdos (ro,noexec,nosuid,nodev)


> > That boot disk says "SYSLINUX..." when it is started. This type of boot 
> > disk works fine with my IDE disk which isn't detected by my ugly BIOS.

> If you don't still have the disk, boot your rescue disk (just like you
> were going to do a fresh install), select a keyboard, activate your
> swap partition, mount your linux partition(s), and then select "Make a
> bootable floppy" from the menu.

And this would create this exact *type* of boot disk?

Thanks a lot, this is great!
Sven
-- 
Powered by Debian GNU/Linux 2.2


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

Re: kernel 2.2.17 boot disk prob! (HELP!)

[Sven Burgener]

Hi all

# file /boot/vmlinuz-*;
/boot/vmlinuz-2.2.15: Linux kernel x86 boot executable bzImage, version 2.2.15 
(herbert@gondor) #1 Tue , RO-rootFS, Normal VGA
/boot/vmlinuz-2.2.17: Linux kernel x86 boot executable bzImage, version 2.2.17 
(herbert@arnor) #1 Sun J, RO-rootFS, root_dev=0x302, Normal VGA
^^
I don't know, but might this be the problem??

TIA
-- 
S. Burgener
Powered by Debian GNU/Linux 2.2


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

kernel 2.2.17 boot disk prob!

[Sven Burgener]

Hi all

Forgive me for sending this mail in a cross-posting fashion, but I
really need some help here. This is what I posted previously to
debian-user:

Thanks in advance for any replies!


On Mon, Jul 03, 2000 at 11:44:05PM +0200, Sven Burgener wrote:
> Hi debs
> 
> I am unable to create a boot disk for my potato box. I just apt-got 
> kernel-image-2.2.17. :)
> 
> Then, in the process of installing the kernel-image deb file, I said 
> "yes" to take /etc/lilo.conf for setting up the boot disk. I also
> chose to format the boot disk.
> 
> Here infos of my system:
> 
> -- /etc/lilo.conf --
> boot=/dev/fd0
> root=/dev/hdb3
> 
> #compact
> install=/boot/boot.b
> map=/boot/map
> delay=20
> vga=normal
> 
> default=Linux
> 
> image=/vmlinuz
>   label=Linux
>   read-only
> # restricted
> # alias=1
> -- /etc/lilo.conf --
> 
> 
> # ls -l /boot
> total 2656
> -rw-r--r--1 root root   265942 Jun  3 19:07 System.map-2.2.15
> -rw-r--r--1 root root   265635 Jun 25 02:16 System.map-2.2.17
> -rw-r--r--1 root root  512 Jul  3 22:10 boot.0200
> -rw-r--r--1 root root  512 Jun  3 20:48 boot.0340
> -rw-r--r--1 root root  512 Jun  3 21:00 boot.0341
> -rw-r--r--1 root root  512 Jun 14 21:20 boot.0800
> -rw-r--r--1 root root 4568 Mai 23 12:48 boot.b
> -rw-r--r--1 root root 4592 Apr 13 11:04 boot.b.preserved
> -rw-r--r--1 root root  612 Mai 23 12:48 chain.b
> -rw-r--r--1 root root  612 Apr 13 11:04 chain.b.preserved
> -rw-r--r--1 root root12294 Jun  3 19:07 config-2.2.15
> -rw-r--r--1 root root20762 Jun 25 01:22 config-2.2.17
> drwxr-xr-x2 root root12288 Jun  3 19:06 lost+found
> -rw---1 root root14336 Jul  3 23:07 map
> -rw-r--r--1 root root  512 Mär  3 20:33 mbr.b
> -rw-r--r--1 root root  640 Mai 23 12:48 os2_d.b
> -rw-r--r--1 root root  644 Jun  3 19:37 os2_d.b.preserved
> -rwxr-xr-x1 root root  1046612 Jun  3 19:07 vmlinuz-2.2.15
> -rw-r--r--1 root root  1042807 Jun 25 02:16 vmlinuz-2.2.17
> 
> 
> # mount
> /dev/hdb3 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
> proc on /proc type proc (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> /dev/hdb1 on /boot type ext2 (rw)
> 
> 
> When booting with the new boot disk, though, I get "L" and then zillions 
> of 0's and 1's. I then have to three-finger-salute the box. :(
> 
> 
> 
> I *want* kernel-image-2.2.17 to work particularly as I had no success in
> building my custom 2.2.16 kernel. (The gettys got locked up and I got
> lots of dumps in the logs)
> 
> Here is a snippet of that (2.2.16): (sorry for the horrid formatting)
> 
> -- /var/log/syslog --
> Jun 24 20:37:41 hp kernel: 
> Jun 24 20:37:41 hp kernel:  free
>sibling
> Jun 24 20:37:41 hp kernel:   task PCstack   pid father child younger 
>older
> Jun 24 20:37:41 hp kernel: init   1 S C17F9EF8  5216 1  0  2142
> Jun 24 20:37:41 hp kernel:sig: 0   : X
> Jun 24 20:37:41 hp kernel: kflushd2 S C17B5FA4  6132 2  1 3
> Jun 24 20:37:41 hp kernel:sig: 0   : X
> Jun 24 20:37:41 hp kernel: kupdate3 S C17B3FB8  6236 3  1 4  
>   2
> Jun 24 20:37:41 hp kernel:sig: 0  fffd : X
> Jun 24 20:37:41 hp kernel: kpiod  4 S 0F00  6980 4  1 5  
>   3
> Jun 24 20:37:41 hp kernel:sig: 0   : X
> Jun 24 20:37:41 hp kernel: kswapd 5 S C17AFFC4  5840 5  184  
>   4
> Jun 24 20:37:41 hp kernel:sig: 0   : X
> 
> [snipped]
> 
> Jun 24 21:12:45 hp kernel: getty  6 S 7FFF 0  4367  1
>2157
> Jun 24 21:12:45 hp kernel:sig: 0   : X
> Jun 24 21:12:53 hp init: Switching to runlevel: 0
> -- /var/log/syslog --
> 
> Forgive me for reporting two problems at once here. :)
> 
> I'd _greatly_ appreciate any help!
> 
> TIA
> -- 
> S. Burgener
> Powered by Debian GNU/Linux 2.2
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 


-- 
S. Burgener
Powered by Debian GNU/Linux 2.2


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