new kernel package ready to use

oh the source is the orginal kernel org source u can build the modules with my config
but u mußt apply the patches .. without (especially the make patch) u cant load module wit 2.6.35 (I said it many times)

if u want i can upload the actual full patched kernel source so u can build what u want


Regards, Gorgone

Hello gorgone,

thanks for the heavy kernel! The included rt2870sta module made my TL-WN727N usb wifi adapter work :)

One thing though:

gorgone Wrote:
-------------------------------------------------------
> 2.6.35.6 is online module whishes are welcome

I would really appreciate if you could include the autofs modules. Without them autofs refuses to work :(

automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required.

Jeffs kernel seems to have them:

#modprobe -l | grep autofs
kernel/fs/autofs/autofs.ko
kernel/fs/autofs4/autofs4.ko

TIA!

Lars

ok i make a new build with autofs if i find it ;-)

Is it possible to publish the kernel sources/headers? I need to compile v4l-dvb for my needs and can't find the needed files...

thanks in advance
murpf

Hello Gorgone,

thank you for your kernels, they work fine for me - except one problem: I've tried to install shorewall yesterday, and could'nt get it to start. The error message has been:

"Your kernel/iptables do not include state match support. No version of Shorewall will run on this system"

Would it be possible to include this state match support (via conntrack, I think?) in your next kernel build?

Thanks a lot (Vielen Dank!)

Anima79

take the source from www.kernel.org

murpf Wrote:
-------------------------------------------------------
> Is it possible to publish the kernel
> sources/headers? I need to compile v4l-dvb for my
> needs and can't find the needed files...
>
> thanks in advance
> murpf

ich dachte ich hab alle iptables teile drin aber ich seh nochmal nach

Anima79 Wrote:
-------------------------------------------------------
> Hello Gorgone,
>
> thank you for your kernels, they work fine for me
> - except one problem: I've tried to install
> shorewall yesterday, and could'nt get it to start.
> The error message has been:
>
> "Your kernel/iptables do not include state match
> support. No version of Shorewall will run on this
> system"
>
> Would it be possible to include this state match
> support (via conntrack, I think?) in your next
> kernel build?
>
> Thanks a lot (Vielen Dank!)
>
> Anima79

Gorgone,

thanks for your help! That would be perfect...

[Super, das wäre nett. Keine Ahnung, was da fehlen könnte. Beim Durchschauen habe ich eigentlich auch gedacht, dass alle Module drin wären. Aber anscheinend passt da wohl doch was nicht... Mann, ich kenn mich mit Linux einfach zu wenig aus :-( ]

Anima79

Hi Gorgone,

I just installed your latest 2.6.35.6-dockstar "heavy" kernel. While it runs without problems, it seems to lack the "standard" ntfs.ko module ? In my special case I would prefer this one over ntfs-3g, since the person for which I am preparing a Dockstar only needs ntfs read support. And he prefers to use ntfs.ko because this driver can be used together with webmin, while webmin does not support mounting a partition using ntfs-3g.

Thx for reading, NanoBot

Hi Gorgone,

is it possible to include the "sisusbvga" and the "hci_usb" kernel-modul in your next kernel build.


Thanks a lot
Robert



Edited 1 time(s). Last edit at 10/07/2010 10:08AM by RobertD.

nont use the ntfs kernel module !!
use ntfs-3g

I am using ntfs-3g right now, and off course it is not a problem to mount ntfs formatted drives ro with ntfs-3g. The only reason why I was missing the ntfs.ko kernel module is that webmin does not support mounting drives using ntfs-3g at all. And the person, for which I am preparing this Dockstar, has nearly no linux knowledges, so it would have been easier to him if he would have been able to use webmin. The other possibility would be to search for an alternative "Disk and Network Filesystems" module for webmin which is capable to handle ntfs-3g instead of ntfs, since the original webmin module does not support ntfs-3g.

Nevertheless, the situation changed in that way, that I was able to create a set of udev-rules for his USB drives. These rules are automatically mounting his drives ro at predefined mount points when they are plugged in. These rules also unmount each of his drives when any of them is unplugged ( not a problem, since they are mounted ro anyway ).

ok i add the ntfs module ..

@NanoBot
Sounds like you could be interested in autofs as well. This way your ntfs partitions get mounted on accessing the mount point (if plugged in) and unmounted after a predefined period of inactivity.

@gorgone
As you are getting many requests, perhaps you want to show us how you build your kernel. This way more experienced users could just do it themselves. Maybe you could provide us your config as well.

I have a working arm build environment here and I have build kernels for my pc hardware before. Anyway, this embedded stuff is new to me :)

Herzlichen Dank im Voraus,

Lars

if u want to build your own kernel follow the jeff kernel thread

i checked my build
autofs is in kernel (v3 and v4) not a module its not nessesary to load it separatly
also all hci_usb drivers xhci ohci uhci hard in kernel no module !

i add sisusbvga ntfs(readonly) fixed contrac

build is on time
i will upload it tomorrow
2.6.35.7 heavy

gorgone Wrote:
-------------------------------------------------------
> i checked my build
> autofs is in kernel (v3 and v4) not a module its
> not nessesary to load it separatly
> also all hci_usb drivers xhci ohci uhci hard in
> kernel no module !
>
> i add sisusbvga ntfs(readonly) fixed contrac
>
> build is on time
> i will upload it tomorrow
> 2.6.35.7 heavy

I referenced your patch files for 2.6.35.4 to compile 2.6.35.7. Can confirm that the new kernel is an improvement: tested the wireless - under Debian Squeeze - with a zd1211 and a p54usb adapter; they both work without any additional software. Just make sure that the route for the WLAN interface is at a higher priority than the ethernet interface:

route add -net 192.168.0.0/24 metric 10 eth0
route delete -net 192.168.0.0/24 eth0

When you upload new kernels, would you also make the respective patch files available.

Delhibelli,
Glad to hear that WiFi adapters are working better for the new kernel. My main problem with Squeeze was that if you connect both ethernet and wifi, they works fine. However, if you boot without ethernet, the wifi was not up. Could you check if you can bring up wifi reliably without ethernet connected? This is the main reason that I cannot use squeeze.
The wifi adapter I used was zd1211.

twinclouds Wrote:
-------------------------------------------------------
> Delhibelli,
> Glad to hear that WiFi adapters are working better
> for the new kernel. My main problem with Squeeze
> was that if you connect both ethernet and wifi,
> they works fine. However, if you boot without
> ethernet, the wifi was not up. Could you check if
> you can bring up wifi reliably without ethernet
> connected? This is the main reason that I cannot
> use squeeze.
> The wifi adapter I used was zd1211.


I've just spent several hours configuring and testing a zd1211 adapter, and can
confirm that the WiFi functions without an ethernet cable being attached at boot-up: as long as the route for the WLAN interface is at a higher priority than the ethernet interface

root@megaslug:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan1
192.168.0.0 * 255.255.255.0 U 10 0 0 eth0

/etc/network/interfaces
***************************
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 192.168.0.231
netmask 255.255.255.0
gateway 0.0.0.0

#p54usb
auto wlan0
iface wlan0 inet static
address 192.168.0.232
netmask 255.255.255.0
gateway 0.0.0.0
wpa-conf /etc/wpa_supplicant.conf

#zd1211
auto wlan1
iface wlan1 inet static
address 192.168.0.233
netmask 255.255.255.0
gateway 0.0.0.0
wpa-conf /etc/wpa_supplicant.conf




wpa_supplicant.conf
@@@@@@@@@@@


# See /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample
# for many more options that you can use in this file.

# This line enables the use of wpa_cli which is used by rc.wireless
# if possible (to check for successful association)
ctrl_interface=/var/run/wpa_supplicant
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

# WPA protected network, supply your own ESSID and WPAPSK here:
network={
scan_ssid=1
ssid="mullip"
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk="AABBCCDDEEFF0123456789"

}

# Plaintext connection (no WPA, no IEEE 802.1X),
# nice for hotel/airport types of WiFi network.
network={
key_mgmt=NONE
priority=0
}

@@@@@@@@

Prior to using kernel 2.6.35.7 I used ifplugd

Dehlibelli Wrote:
-------------------------------------------------------
..................
> I've just spent several hours configuring and
> testing a zd1211 adapter, and can
> confirm that the WiFi functions without an
> ethernet cable being attached at boot-up: as long
> as the route for the WLAN interface is at a higher
> priority than the ethernet interface
....................
>
A couple of questions:

1. Where and how you set the priorities of the network interfaces?

2. Do you downloaded he kernel 2.6.35.7 by gorgone or compiled yourself?

sral Wrote:
-------------------------------------------------------
> @NanoBot
> Sounds like you could be interested in autofs as
> well. This way your ntfs partitions get mounted on
> accessing the mount point (if plugged in) and
> unmounted after a predefined period of
> inactivity.

That looks like a possible alternative solution. Do you know if autofs can be used togethers with UUIDs to ensure that the partitions are always mounted at the same predefined mountpoints ?

@gorgone
thanks in advance for adding the ntfs kernel module.

Ich bin ja erstaunt, wieviele deutschsprachige User hier so unterwegs sind. Offenbar haben Atelco und Co. in Deutschland eine Menge Dockstars verkauft. Oder seit ihr auch alle über das Streamboard zum Dockstar gekommen, so wie z.B. gorgone und ich ?

C.U. NanoBot

2.6.35.7 is online
fresh module list



Edited 1 time(s). Last edit at 10/08/2010 06:43PM by gorgone.

all u need is the usbmount package
than all inserted drives are mounted automaticly

gorgone Wrote:
-------------------------------------------------------
> all u need is the usbmount package
> than all inserted drives are mounted automaticly

At first I tried to use usbmount, but depending on the order the USB devices are plugged in, they will be mounted on different mountpoints everytime. The same partition might be /media/usb0 the first time, and /media/usb2 the next time etc. Since the drives are to be shared through samba, I need them to be mounted at the same predefined mountpoints regardless of the order in which the drives are connected and removed. My next try was a combination of udev-rules ( to assign a fixed alias name to the device node for each drive depending on the serial ) and usbmount. But then I found, that usbmount is not neccessary at all, all I would like to achieve is possible using only udev-rules.

Here is an example of the solution I am using now: I want a specific USB pendrive ( which is colored black ) to be automatically mounted at /media/schwarz, when it is connected, and to be unmounted, when it is removed.

I created the desired mountpoint /media/schwarz with mkdir.

Next, I read the serial number of the stick using lsusb -v, which is AA04012700007459. Of course I could have used udevadm info to get more device specific attributes, but the serial number is enough to identify this USB device. So I created /etc/udev/rules.d/60-usbmount.rules containing three rules

KERNEL=="sd*", ATTRS{serial}=="AA04012700007459", SYMLINK="schwarz%n"
KERNEL=="sd*", ATTRS{serial}=="AA04012700007459", ACTION=="add", RUN+="/bin/mount /dev/schwarz1",OPTIONS="last_rule"
KERNEL=="sd*", ATTRS(serial)=="AA04012700007459", ACTION=="remove", RUN+="/bin/umount -l /media/schwarz",OPTIONS="last_rule"

and added this line to /etc/fstab

/dev/schwarz1 /media/schwarz ntfs-3g ro,noatime,fmask=333,dmask=222,locale=de_DE.utf8 0 0

That's it, no need for usbmount at all. Fortunately, the udev-rules are processed before fstab during a system startup, so the alias name for the device node, /dev/schwarz1 in this example, is set before fstab is processed. Therefore it doesn't matter if the stick is already plugged in during bootup, or if it is hot plugged with the system already running. Whenever the stick is detected, it will be mounted as /media/schwarz, and whenever it is removed, it will be unmounted ( perhaps after a few minutes, due to the -l parameter ).

There is even a better possibility, which I have not tested yet. That is to dynamically create the mount point using an additional udev-rule when the usb drive is detected and to delete it when the stick is removed by another rule. That should make it possible to see from a network computer if a specific drive is plugged in and available or not.

C.U. NanoBot

im a quick and dirty user
i add simply one line to the mount script (00_create_model_symlink)


# If the symlink does not yet exist, create it.
test -e "/mnt/sambafreigabe/$name" || ln -sf "$UM_MOUNTPOINT" "/mnt/sambafreigabe/$name"

modify where ever u want ;-)

twinclouds Wrote:
-------------------------------------------------------
> Dehlibelli Wrote:
> --------------------------------------------------
> -----
> ..................
> > I've just spent several hours configuring and
> > testing a zd1211 adapter, and can
> > confirm that the WiFi functions without an
> > ethernet cable being attached at boot-up: as
> long
> > as the route for the WLAN interface is at a
> higher
> > priority than the ethernet interface
> ....................
> >
> A couple of questions:
>
> 1. Where and how you set the priorities of the
> network interfaces?
>
> 2. Do you downloaded he kernel 2.6.35.7 by gorgone
> or compiled yourself?

1. Add the following lines to /etc/rc.local

/sbin/route add -net 192.168.0.0/24 metric 10 eth0
/sbin/route delete -net 192.168.0.0/24 eth0

Change the network address and the mask to suit your network. The default metric is 0 (highest priority); therefore metric 10 is a lower priority.

2. I compiled the kernel myself. Gorgone's patches for 2.6.35.4 can be amended for 2.6.35.7
I basically followed Jeff's instructions: Howto: Build a new Debian kernel with LED support, and then followed Gorgone's
instructions to set the LEDs. The kernel can be compiled under either Debian Squeeze or Ubuntu 10.04. To compile under Ubuntu follow Rudolf's instructions. I can confirm that the code produced under Debian and Ubuntu is identical and compatible.

Does this kernel have hfs+ read/write (i.e., macintosh-formatted disk) built-in? If not, what are the steps that need to be taken to build in that kernel module?

Thanks in advance.

new kernel with hfs and hfs+ support online

Using the new bootstrap.deb file (025) and the new kernel by gornone, the wifi usb adapter works perfectly without set the priority. I don't know if this is the new bootstrap installation or the new kernel did the trick. In any case, it works fine on Squeeze now!

Hello Gorgone,

Shorewall now works perfectly! Thank you for your time and efforts!

Anima79