new kernel package ready to use

is it possible to include the modem driver cdc-acm in the next kernel version please.
thank you for your grat work.

remo

modem ??
why that

NanoBot Wrote:
-------------------------------------------------------
> 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 ?

From what I saw you can use UUIDs as well as labels. But it seems to need a newer protocol version than autofs v3/v4 which are in the kernel according to gorgone.

I will look into this the next days.

Lars

i allways use uuid if its possible and it works without any problem
and yes u can use it on fstab

gorgone Wrote:
-------------------------------------------------------
> i allways use uuid if its possible and it works
> without any problem

UUID always is the most specific way.

> and yes u can use it on fstab

Autofs isn't configured through fstab but through separate config files. But anyway it supports UUIDs as well.

The advantage over pure udev rules is that automount mounts on demand and also unmounts after timeout. That's quite convenient for rw mounts. I plan to use it for a ntfs formatted multimedia HDD which does not turn on its mediacenter when its connected through usb. Having to unmount manually instead of just unplugging would be really annoying...

my drives all automaticly mounted with usbmount in my preselected dirs with preselected names
i unmount this drives with a litle script started over a self build webinterface.... so there are NO problems

oh man autofs autofs autofs ....... and ntfs ntfs ntfs *grml*
here a autofs tutorial for linux user :-P

KLICK - zur strafe wegen ständigen wiederholens des wortes ntfs



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

hi gorgone
i need the cdc-acm driver for mit usb receiverstick CUL ( www.busware.de). because i want to use the dockstar as my homeautomationserver (http://www.koeniglich.de/fhem/fhem.html). so it will be great to have the driver in the next relase.

thank you
remo

ok wenn ich ihn finde bau ich ihn ein :-P
ich hab nachgesehen der is drin
einen speziellen cdc-acm gibts nicht
alle cdcs sind aktv

│ │                                                               {M} Multi-purpose USB Networking Framework                                                                                           │ │
  │ │                                                               <M>   ASIX AX88xxx Based USB 2.0 Ethernet Adapters                                                                                   │ │
  │ │                                                               -M-   CDC Ethernet support (smart devices such as cable modems)                                                                      │ │
  │ │                                                               <M>   CDC EEM support                                                                                                                │ │
  │ │                                                               <M>   Davicom DM9601 based USB 1.1 10/100 ethernet devices                                                                           │ │
  │ │                                                               <M>   SMSC LAN75XX based USB 2.0 gigabit ethernet devices                                                                            │ │
  │ │                                                               <M>   SMSC LAN95XX based USB 2.0 10/100 ethernet devices                                                                             │ │
  │ │                                                               <M>   GeneSys GL620USB-A based cables                                                                                                │ │
  │ │                                                               <M>   NetChip 1080 based cables (Laplink, ...)                                                                                       │ │
  │ │                                                               <M>   Prolific PL-2301/2302 based cables                                                                                             │ │
  │ │                                                               <M>   MosChip MCS7830 based Ethernet adapters                                                                                        │ │
  │ │                                                               -M-   Host for RNDIS and ActiveSync devices (EXPERIMENTAL)                                                                           │ │
  │ │                                                               <M>   Simple USB Network Links (CDC Ethernet subset)                                                                                 │ │
  │ │                                                               [*]     ALi M5632 based 'USB 2.0 Data Link' cables                                                                                   │ │
  │ │                                                               [*]     AnchorChips 2720 based cables (Xircom PGUNET, ...)                                                                           │ │
  │ │                                                               [*]     eTEK based host-to-host cables (Advance, Belkin, ...)                                                                        │ │
  │ │                                                               [*]     Embedded ARM Linux links (iPaq, ...)                                                                                         │ │
  │ │                                                               [*]     Epson 2888 based firmware (DEVELOPMENT)                                                                                      │ │
  │ │                                                               [*]     KT Technology KC2190 based cables (InstaNet)

Edited 1 time(s). Last edit at 10/10/2010 10:32AM by gorgone.

hallo gorgone
leider wird mei stick nicht erkannt und das modul /kernel/drivers/usb/class/cdc-acm.ko ist auch nicht auffindbar.
ist es möglich, dass wir nicht vom selben treiber sprechen?

gruss
remo

sorry hast recht wird grad gebaut ich erweitere auch gleich usbgadget support mit
2.6.35.7.2 ist online module liste auch



Edited 2 time(s). Last edit at 10/10/2010 03:36PM by gorgone.

hallo gorgone
cdc_acm läut perfekt. vielen dankund ein gruss.
remo

Sorry to use the emotive terms again.. but I have automount working :)
I built my own kernel with autofs and autofs4 as modules (not directly built into the kernel) and that did the trick. In the end only autofs4 gets loaded. So I guess autofs was interfering before leading to my error message.

@gorgone
Maybe you want to change that in your config as automount is rendered useless in you kernel so far.

gorgone Wrote:
-------------------------------------------------------
> my drives all automaticly mounted with usbmount in
> my preselected dirs with preselected names
> i unmount this drives with a litle script started
> over a self build webinterface.... so there are NO
> problems

No offence but I think there is a problem: you have to go to a webinterface to umount :P
My setup now mounts automatically on access of the mountpoint. When it mounts the orange led is turned on flashing in addition to the green one. When nothing accesses the mountpoint anymore umount is performed after 15s of timeout turning the orange led off again.

So:
green -> not mounted/save to remove,
green + orange flashing -> mounted/do not remove.

That has a really high WAF (woman acceptance factor) :D

Thanks again for your effort, gorgone!

Lars

gorgone Wrote:
-------------------------------------------------------
> Now 2.6.35.7.2 online
>
> fixed contrac sisusbvga(+consoleswitch)
> ntfs(readonly) hfs hfs+ support
> usbgadgets addet
>
hi, i don't understand "usbgadgets addet", do you mean "usbgadgets added".
And if so, does it mean what we could use "The File-backed Storage Gadget (FSG)" (provides support for the USB Mass Storage class) and we can do some usb slave emulation ?
It could be usefull for a lots of thing!
correct me if i'm wrong
regards



Edited 2 time(s). Last edit at 10/14/2010 09:40AM by qdftowner.

look @ the modulelist

Hallo Gorgone
hast du den treiber für den LM75 im kernel drin?

gruss remo

Device Drivers --->
<*> I2C support --->
[*] Enable compatibility bits for old user-space
<*> I2C device interface
[*] Autoselect pertinent helper modules
I2C Hardware Bus support --->
<*> GPIO-based bitbanging I2C
<*> Marvell mv64xxx I2C Controller

z.B. als Modul den LM75
<M> Hardware Monitoring support --->
<M> National Semiconductor LM75 and compatibles

hab noch n paar kleine sachn gefunden die ich ändern will dann seh ich nach

fixed i2c add additional code to sheevaplug.c

static unsigned int sheevaplug_mpp_config[] __initdata = {
+        MPP8_TW_SDA,
+        MPP9_TW_SCK,

i2c-core: driver [lm75] registered
i2c i2c-0: found normal entry for adapter 0, addr 0x48
i2c i2c-0: master_xfer[0] W, addr=0x48, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x49
i2c i2c-0: master_xfer[0] W, addr=0x49, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x4a
i2c i2c-0: master_xfer[0] W, addr=0x4a, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x4b
i2c i2c-0: master_xfer[0] W, addr=0x4b, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x4c
i2c i2c-0: master_xfer[0] W, addr=0x4c, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x4d
i2c i2c-0: master_xfer[0] W, addr=0x4d, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x4e
i2c i2c-0: master_xfer[0] W, addr=0x4e, len=0
i2c i2c-0: found normal entry for adapter 0, addr 0x4f
i2c i2c-0: master_xfer[0] W, addr=0x4f, len=0

little mount problems fixed
new kernel online



Edited 1 time(s). Last edit at 10/18/2010 06:06AM by gorgone.

hallo gorgone
danke für deinen super support. leider bootet der kernel nicht fertig.
es wird nach der /lib/kernel.....modules.dep gesucht, welche nicht gefunden wird.
linux startet in eine notshell: initramfs

modprobe: FATAL: Could not load /lib/modules/2.6.35.7-dockstar/modules.dep: No such file or directory

udevadm[1106]: error getting socket: Address family not supported by protocol

Begin: Waiting for root file system ... done.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
FATAL: Could not load /lib/modules/2.6.35.7-dockstar/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35.7-dockstar/modules.dep: No such file or directory
ALERT! /dev/sda1 does not exist. Dropping to a shell!
(initramfs)


hast du einen tip?

gruss
remo



Edited 1 time(s). Last edit at 10/18/2010 11:26PM by appi.

sorry kein plan
depmod -a
mal ausgeführt ?

Hallo gorgone
der neueste Kernel funktioniert def. nicht korrekt. Ich habe es 2 mal versucht ohne erfolg nach dem upgrade auf den nuesten Kernel von dir, ist das system nicht mehr boot fähig.
Nach dem zurückkopieren von /boot und /Modules läuft es wieder.

gruss
remo

kannst du mal mit dem seriellen zugang ein log machen ?
weil hier läuft alles
MyLog



Edited 1 time(s). Last edit at 10/20/2010 09:21AM by gorgone.

Hi Gorgone,

bei mir will die Dockstar mit dem neuen Kernel auch nicht starten. Wo finde ich denn das Logfile? Oder kann man das nur über die serielle Schnittstelle auslesen? Ein CA-42 Kabel hätte ich schon mal da.
Darf man eigentlich nach der Installation deiner Kernel noch mit apt-get upgrade die Kernel aktualisieren lassen, oder muss man das verhindern?

Liebe Grüße!

ja nur seriell wenns nicht startet
das log was ich angehängt habe ist mit dem kernel entstanden
es wäre gut zu wissen woran es hängt

Ich sehe das Problem auch, hier das Log ...

http://pastebin.com/p8aNAUJJ

Wolfgang

Der Ordner /lib/modules/2.6.35.7-dockstar existiert mit dem neuen Kernel nicht.



Edited 3 time(s). Last edit at 10/20/2010 11:16AM by Andy.

gorgone Wrote:
-------------------------------------------------------
> ja nur seriell wenns nicht startet
> das log was ich angehängt habe ist mit dem kernel
> entstanden
> es wäre gut zu wissen woran es hängt

Alles klar, dann werde ich mal das Kabel löten und auch meinen Log posten. Hast du noch eine Antwort auf die Frage, ob man ein Kernelupdate mittels apt-get upgrade ausführen darf? Wird da der Kernel von dir wieder überschrieben?

apt-get update ersetzt den von mir gebauten
durch den kirkwood wenn dieser davor installiert war
mein install script installiert keinen kirkwood sondern nur den eigenen der nicht dadurch
gefährdet ist ersetzt zu werden

@andy
sicher ?
ich sehe /opt/dockstarheavy.deb#deb/CONTENTS/lib/modules/2.6.35.7-dockstar

Irgendwie kommt mir das control.tar.gz in dem aktuellen Kernel-Paket etwas magersüchtig vor:

$ ar tv dockstarheavy.deb 
rw-r--r-- 0/0      4 Oct 18 12:32 2010 debian-binary
rw-r--r-- 0/0    356 Oct 18 12:32 2010 control.tar.gz
rw-r--r-- 0/0 10610997 Oct 18 12:33 2010 data.tar.gz

Da ist nur ein "control" File drin. Ich schätze mal, dass bei der Installation die Initial-Ramdisk nicht gebaut wird.

nö is richtig die is nur 302 byte
inhalt

Package: dockstar.kandm.heavy
Version: 2.6.35.7.3
Section: misc
Priority: extra
Architecture: all
Depends:
Installed-Size: 15000
Maintainer: Gorgone Impertinence <gorgone@debian.com>
Homepage: http://streamboard.gmc.to
Description: Kernel und Module 2.6.35.7.3 Dockstar Multimedia Wireless (heartbeat)

mehr steht da nicht drin

ich baue den nochmal neu und lad den gleich hoch



Edited 1 time(s). Last edit at 10/20/2010 03:01PM by gorgone.

Ich vermisse dann irgendwie die initial ramdisk. In data.tar.gz ist uInitrd auch nicht enthalten. Wo soll die denn herkommen?