Kernel 2.6.30

View: New views
11 Messages — Rating Filter:   Alert me  

Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Good news:

kernel 2.6.30 is out and cloop + aufs are working!!!

I had only to edit config.mk from aufs source ( aufs2-standalone ) and delete "y" from CONFIG_AUFS_DEBUG


Re: Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


stirner wrote:
Good news:

kernel 2.6.30 is out and cloop + aufs are working!!!

I had only to edit config.mk from aufs source ( aufs2-standalone ) and delete "y" from CONFIG_AUFS_DEBUG
Another thing:

if you have knoppix in a  usb pendrive remember to edit linuxrc in minirt.gz and change insmod libusual.ko to insmod usb-libusual.ko.

Max

Re: Kernel 2.6.30

by Daryl Styrk :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jun 10, 2009 at 12:58:10PM -0700, stirner wrote:

>
>
>
> stirner wrote:
> >
> >
> > Good news:
> >
> > kernel 2.6.30 is out and cloop + aufs are working!!!
> >
> > I had only to edit config.mk from aufs source ( aufs2-standalone ) and
> > delete "y" from CONFIG_AUFS_DEBUG
> >
> >
> >
>
> Another thing:
>
> if you have knoppix in a  usb pendrive remember to edit linuxrc in minirt.gz
> and change insmod libusual.ko to insmod usb-libusual.ko.
>

What does this do?  Why?

--
Daryl Styrk
Naples FL, USA


--
To UNSUBSCRIBE, email to debian-knoppix-request@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Kernel 2.6.30

by Klaus Knopper-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Jun 10, 2009 at 12:58:10PM -0700, stirner wrote:

> stirner wrote:
> >
> >
> > Good news:
> >
> > kernel 2.6.30 is out and cloop + aufs are working!!!
> >
> > I had only to edit config.mk from aufs source ( aufs2-standalone ) and
> > delete "y" from CONFIG_AUFS_DEBUG
> >
> >
> >
>
> Another thing:
>
> if you have knoppix in a  usb pendrive remember to edit linuxrc in minirt.gz
> and change insmod libusual.ko to insmod usb-libusual.ko.

Usually that's statically compiled-in in the kernel used in Knoppix. I'm
also thinking about putting cloop and aufs into the static kernel, so no
modprobing is necessary in the initial ramdisk.

On the other hand, modprobing cloop was also making sure that the
modules and kernel matched before mounting the compressed part.

Regards
-Klaus


--
To UNSUBSCRIBE, email to debian-knoppix-request@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Kernel 2.6.30

by Klaus Knopper-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

On Wed, Jun 10, 2009 at 12:06:32PM -0700, stirner wrote:
>
>
> Good news:
>
> kernel 2.6.30 is out and cloop + aufs are working!!!

I tried aufs2-29  from aufs2-standalone with 2.6.30-rc8 a few days ago,
and it die NOT work out (compile time errors because of redefined
functions that apparently had been turned into macros).

Which branch of the aufs2-standalone.git did you use? Maybe I just
missed something.

Of course I would be very happy to include 2.6.30 in the next release
already, currently I'm working with a prerelease based on 2.6.29.7.

Regards
-Klaus


--
To UNSUBSCRIBE, email to debian-knoppix-request@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Klaus Knopper-2 wrote:
Hello,

On Wed, Jun 10, 2009 at 12:06:32PM -0700, stirner wrote:
>
>
> Good news:
>
> kernel 2.6.30 is out and cloop + aufs are working!!!

I tried aufs2-29  from aufs2-standalone with 2.6.30-rc8 a few days ago,
and it die NOT work out (compile time errors because of redefined
functions that apparently had been turned into macros).

Which branch of the aufs2-standalone.git did you use? Maybe I just
missed something.

Of course I would be very happy to include 2.6.30 in the next release
already, currently I'm working with a prerelease based on 2.6.29.7.

Regards
-Klaus


--
To UNSUBSCRIBE, email to debian-knoppix-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
There not a 2.6.30 branch so I did checkout origin/aufs2 ( without a version ) to have the latest one.

Cheers

Max

Re: Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Daryl Styrk wrote:
On Wed, Jun 10, 2009 at 12:58:10PM -0700, stirner wrote:
>
>
>
> stirner wrote:
> >
> >
> > Good news:
> >
> > kernel 2.6.30 is out and cloop + aufs are working!!!
> >
> > I had only to edit config.mk from aufs source ( aufs2-standalone ) and
> > delete "y" from CONFIG_AUFS_DEBUG
> >
> >
> >
>
> Another thing:
>
> if you have knoppix in a  usb pendrive remember to edit linuxrc in minirt.gz
> and change insmod libusual.ko to insmod usb-libusual.ko.
>

What does this do?  Why?

--
Daryl Styrk
Naples FL, USA


--
To UNSUBSCRIBE, email to debian-knoppix-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
To remaster a knoppix with a new kernel you have to compile, at least,  cloop and aufs.



Re: Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Klaus Knopper-2 wrote:
Hello,

I tried aufs2-29  from aufs2-standalone with 2.6.30-rc8 a few days ago,
and it die NOT work out (compile time errors because of redefined
functions that apparently had been turned into macros).

Which branch of the aufs2-standalone.git did you use? Maybe I just
missed something.

Of course I would be very happy to include 2.6.30 in the next release
already, currently I'm working with a prerelease based on 2.6.29.7.

Regards
-Klaus
I was to fast:

there's no problem with usb, but I can't  boot the cdrom iso: it hangs at "looking for cd in /dev/hdc".

I tried: failsafe, nodma, cdrom=hdc

If I boot with "debug" and before the hang do a "cat /dev/hd" there is nothing from the console.
It i do the same (at the same point) with the 2.6.29 kernel I've a lot of garbage from the console.
The device was recognized as /dev/hdc and the script set the dma to 1.
I tried with qemu/kqemu.

Cheers

Max

Re: Kernel 2.6.30

by Klaus Knopper-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

On Thu, Jun 11, 2009 at 06:26:48AM -0700, stirner wrote:

> Klaus Knopper-2 wrote:
> >
> > Hello,
> >
> > I tried aufs2-29  from aufs2-standalone with 2.6.30-rc8 a few days ago,
> > and it die NOT work out (compile time errors because of redefined
> > functions that apparently had been turned into macros).
> >
> > Which branch of the aufs2-standalone.git did you use? Maybe I just
> > missed something.
> >
> > Of course I would be very happy to include 2.6.30 in the next release
> > already, currently I'm working with a prerelease based on 2.6.29.7.
> >
> > Regards
> > -Klaus

Thanks for the hint about using the master aufs2 version instead of the
Kernel 2.6.29, indeed it works with 2.6.30. :-)

> I was to fast:
>
> there's no problem with usb, but I can't  boot the cdrom iso: it hangs at
> "looking for cd in /dev/hdc".
>
> I tried: failsafe, nodma, cdrom=hdc
>
> If I boot with "debug" and before the hang do a "cat /dev/hd" there is
> nothing from the console.
> It i do the same (at the same point) with the 2.6.29 kernel I've a lot of
> garbage from the console.
> The device was recognized as /dev/hdc and the script set the dma to 1.
> I tried with qemu/kqemu.

This may be a problem related to the now somewhat Knoppix-specific
mixture of IDE and SATA/PATA drivers. Please make sure that you don't
have overlapping drivers in the IDE and SATA/PATA section of your kernel
configuration. In some cases, the best matching driver "wins" and does
not get blocked by the IDE/SATA equivalent, but sometimes this does not
work. Also, you need to enable iso9660 filesystem support. In general,
please compare your newly compiled kernels .config with the one from the
older kernel version. You may have missed a few options, or compiled
them as modules instad of statically compiled in.

Maybe we should in general switch from using the old (but stable) IDE
drivers to a completely SATA/PATA based configuration in order to avoid
conflicts between IDE and PATA? Many distributions seem to use PATA
exclusively instead of IDE today.

Regards
-Klaus


--
To UNSUBSCRIBE, email to debian-knoppix-request@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
On Friday 12 June 2009, you wrote:


> Hi,
>
> On Thu, Jun 11, 2009 at 06:26:48AM -0700, stirner wrote:
> > Klaus Knopper-2 wrote:
> > >
> > > Hello,


> This may be a problem related to the now somewhat Knoppix-specific
> mixture of IDE and SATA/PATA drivers. Please make sure that you don't
> have overlapping drivers in the IDE and SATA/PATA section of your kernel
> configuration. In some cases, the best matching driver "wins" and does
> not get blocked by the IDE/SATA equivalent, but sometimes this does not
> work. Also, you need to enable iso9660 filesystem support. In general,
> please compare your newly compiled kernels .config with the one from the
> older kernel version. You may have missed a few options, or compiled
> them as modules instad of statically compiled in.
>
> Maybe we should in general switch from using the old (but stable) IDE
> drivers to a completely SATA/PATA based configuration in order to avoid
> conflicts between IDE and PATA? Many distributions seem to use PATA
> exclusively instead of IDE today.
>
> Regards
> -Klaus
>


Hi,


thanks for the prompt reply!!!


There are very few differences form my 2.6.29 and 2.6.30 config, here's the relevant part.


--- /minik-2630/boot/config-2.6.30 2009-06-10 22:08:23.000000000 +0200
+++ /minik-2629/boot/config-2.6.29 2009-04-02 11:11:50.000000000 +0200
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
-# Linux kernel version: 2.6.30
-# Wed Jun 10 16:19:56 2009
+# Linux kernel version: 2.6.29
+# Wed Apr 1 19:54:15 2009


-CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_TIMINGS=y
CONFIG_IDE_ATAPI=y
CONFIG_IDE_LEGACY=y
@@ -1467,16 +1443,11 @@
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
-CONFIG_SCSI_MPT2SAS=m
-CONFIG_SCSI_MPT2SAS_MAX_SGE=128
-# CONFIG_SCSI_MPT2SAS_LOGGING is not set
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_FLASHPOINT is not set
# CONFIG_LIBFC is not set
-# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
-# CONFIG_FCOE_FNIC is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
@@ -1546,7 +1517,6 @@
CONFIG_SCSI_DH_HP_SW=m
# CONFIG_SCSI_DH_EMC is not set
CONFIG_SCSI_DH_ALUA=m
-# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
@@ -1622,7 +1592,7 @@
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
-CONFIG_MD_RAID6_PQ=m
+CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m

-# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
+# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed;


#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
-CONFIG_USB_STORAGE_DATAFAB=m
-CONFIG_USB_STORAGE_FREECOM=m
-CONFIG_USB_STORAGE_ISD200=m
-CONFIG_USB_STORAGE_USBAT=m
-CONFIG_USB_STORAGE_SDDR09=m
-CONFIG_USB_STORAGE_SDDR55=m
-CONFIG_USB_STORAGE_JUMPSHOT=m
-CONFIG_USB_STORAGE_ALAUDA=m
+CONFIG_USB_STORAGE_DATAFAB=y
+CONFIG_USB_STORAGE_FREECOM=y
+CONFIG_USB_STORAGE_ISD200=y
+CONFIG_USB_STORAGE_USBAT=y
+CONFIG_USB_STORAGE_SDDR09=y
+CONFIG_USB_STORAGE_SDDR55=y
+CONFIG_USB_STORAGE_JUMPSHOT=y
+CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_STORAGE_ONETOUCH is not set
-CONFIG_USB_STORAGE_KARMA=m
+CONFIG_USB_STORAGE_KARMA=y
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
CONFIG_USB_LIBUSUAL=y


@@ -3147,7 +3095,7 @@
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
-CONFIG_USB_SERIAL_CP210X=m
+CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
@@ -3183,14 +3131,12 @@
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
-CONFIG_USB_SERIAL_QUALCOMM=m
# CONFIG_USB_SERIAL_SPCP8X5 is not set
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIEMENS_MPI=m
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
-# CONFIG_USB_SERIAL_SYMBOL is not set
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
@@ -3213,6 +3159,10 @@
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
+CONFIG_USB_PHIDGET=m
+CONFIG_USB_PHIDGETKIT=m
+CONFIG_USB_PHIDGETMOTORCONTROL=m
+CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m


Best wishes



Max


--
KMail: 1.11.2
linux 2.6.29.1 i686
ven 12 giu 2009 09:53:47 CEST



Re: Kernel 2.6.30

by stirner :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


stirner wrote:
On Friday 12 June 2009, you wrote:

> Hi,
>
> On Thu, Jun 11, 2009 at 06:26:48AM -0700, stirner wrote:
> > Klaus Knopper-2 wrote:
> > >
> > > Hello,

> This may be a problem related to the now somewhat Knoppix-specific
> mixture of IDE and SATA/PATA drivers. Please make sure that you don't
> have overlapping drivers in the IDE and SATA/PATA section of your kernel
> configuration. In some cases, the best matching driver "wins" and does
> not get blocked by the IDE/SATA equivalent, but sometimes this does not
> work. Also, you need to enable iso9660 filesystem support. In general,
> please compare your newly compiled kernels .config with the one from the
> older kernel version. You may have missed a few options, or compiled
> them as modules instad of statically compiled in.
>
> Maybe we should in general switch from using the old (but stable) IDE
> drivers to a completely SATA/PATA based configuration in order to avoid
> conflicts between IDE and PATA? Many distributions seem to use PATA
> exclusively instead of IDE today.
>
> Regards
> -Klaus
>
It should be a qemu problem: it works in virtual box.

Max