=== maco_ is now known as maco
[02:59] <Leon_Nardella> Anyone working on the ex4 freezes in Jaunty? I'm using the latest mainline build from the kernel-ppa and it seems to be free of this bug.
[03:00]  * Leon_Nardella forgot to mention this is that bug that manifests under heavy IO
=== _Purple_ is now known as _Purple_away
=== _Purple_away is now known as _Purple_
[10:00] <Kamping_Kaiser> Hi, could someone explain the difference between https://launchpad.net/ubuntu/+source/linux and http://packages.ubuntu.com/search?keywords=linux-image-generic (or http://packages.ubuntu.com/search?keywords=linux )
[10:01] <Kamping_Kaiser> the LP link indicates that hardy-security and hardy-updates share the same kernel versions, but p.u.c has them marked as different versions still
=== asac_ is now known as asac
=== Omegamoon is now known as Omegamoon|away
[11:50] <maxb> Kamping_Kaiser: In the LP link, you are looking at the "linux" source package. In the p.u.c link, you are looking at the "linux-meta" source package
[11:51] <maxb> Yes, it's a little confusing that the "linux" binary package is built by the "linux-meta" source package, not the "linux" source package
[11:51] <Kamping_Kaiser> maxb, ah. so on LP i need to be looking at 'linux-meta' instead?
[11:53] <Kamping_Kaiser> I should probably move a bug report then, since it relates to the linux-meta packages not linux.
[11:53] <maxb> Well, that depends which package you're actually interested in :-)
[11:54] <Kamping_Kaiser> linux-image-386
[13:06] <Kamping_Kaiser> 350 bugs against linux-meta. criky. not sure moving the bug in there is going to help it
[13:10] <Kamping_Kaiser> How can I mark https://bugs.launchpad.net/bugs/342638 as affecting linux-meta not linux ?
[13:10] <ubot3> Malone bug 342638 in linux "linux-image-{generic,386} in -security uninstallable without -updates repository." [Undecided,New] 
[14:01] <erle-> did anyone try to build kernel 2.6.29.1 with make-kpkg?
=== k-s[AWAY] is now known as k-s
[14:25] <asac> is there a hackish way to force a different vendor/product id for a usb device (e.g. so i can test a driver with a new device without rebuilding the kernel)?
[14:27] <Kamping_Kaiser> hex editor + kernel module? hackish enough? ;)
[14:28] <asac> hehe
[14:28] <asac> good idea
[14:33] <asac> too bad ... cant find the id ;)
[14:33] <asac> is there anything i can look for in the module to find the right spot?
[14:34] <asac> its cdc_ether ;)
[14:34] <erle-> are the "mainline" kernels patched?
[14:34] <erle-> i thougt that are vanilla kernels
[14:36] <asac> heh. i think i found it :)
[14:36] <asac> now i am scared ;)
[14:38] <anubhav> asac: why not just recompile the module with your vend id and prod id
[14:38] <asac> anubhav: hmm. whats the best way to just build a module?
[14:39] <anubhav> offcourse you will need sources
[14:39] <asac> i dont have a built tree here ;)
[14:39] <anubhav> you are building against the standard ubuntu kerenel?
[14:40] <asac> anubhav: i want to do that because i this thing also has some drivers that are not in mainline
[14:40] <asac> so yes
[14:40] <asac> i want to build a patched cdc_ether.ko
[14:40] <asac> against current jaunty
[14:42] <asac> darn ... now i cannot get the raw file from kernel.ubuntu.com ... gives me a 0 bytes download
[14:43] <asac> good now it worked
[14:44] <erle-> shouldn't a vanilla kernel build with a config of the ubuntu mainline kernel? (same kernel version!!)
[14:45] <asac> anubhav: so i have the patched module source ... what i can do now?
[14:46] <amitk> erle-: mainline kernels are stock linus' trees with the ubuntu config
[14:46] <erle-> amitk, i know
[14:46] <erle-> but it doesn't build here ...
[14:46] <erle-> Makefile:529: /usr/src/linux-source-2.6.29/arch/xen/Makefile: No such file or directory
[14:46] <erle-> make[1]: *** No rule to make target `/usr/src/linux-source-2.6.29/arch/xen/Makefile'. Stop.
[14:46] <erle-> make: *** [conf.vars] Error 2
[14:46] <erle-> i have no idea, why
[14:46] <erle-> i don't care about xen
[14:47] <asac> amitk: do you have any clue? i need to just build a single kernel module file i have here 
[14:47] <amitk> asac: cdc-ether is compiled in?
[14:47]  * amitk checking
[14:48] <asac> amitk: its a module ... i need to build it with more device ids
[14:48] <amitk> aah
[14:48] <asac> amitk: http://paste.ubuntu.com/144184/
[14:49] <amitk> asac: yes, it can be done AFAIK. Just looking for the right /sys file to put that info in
[14:49] <asac> the other idea was to use hexedit ;)
[14:49] <asac> my first hope was that i can force a different vendor/product id on that device somehow
[14:49] <asac> just to test
[14:50] <amitk> asac: /sys/module/cdc_ether/drivers/usb:cdc_ether/new_id
[14:50] <erle-> now i use the sourcecode from the mainline thing and the config from the mainline thing and it still does not build ...
[14:51] <asac> amitk: what can i do with that?
[14:51] <amitk> asac: still looking for the exact incantation
[14:51] <erle-> does nobody have an idea?
[14:51] <amitk> erle-: it doesn't always build and it is too early on a weekend for me to know why :)
[14:52] <erle-> it says he cannot build xen or something
[14:52] <erle-> but there is no xen in the source code which actually should have been built
[14:53] <erle-> do you use make-kpkg to build?
[14:53] <erle-> maybe it is the tool failing
[14:58] <asac> ok so its a colon separated list
[14:58] <asac> amitk: http://paste.ubuntu.com/144189/
[14:59] <asac> thats what i found on google :)
[14:59] <asac> now i have to find the values for everything  before vendor
[15:00] <erle-> it build now
[15:00] <erle-> but i had to mod the configuration manually ...
[15:01] <asac> hmm ... not sure if its the same for usb though
[15:02] <amitk> asac: do a 'modinfo cdc-ether'
[15:02] <amitk> the format of the alias strings might work
[15:02] <asac> looking
[15:02] <amitk> it is a concatenated string
[15:02] <amitk> v=vendor, p=productid, etc.
[15:04] <asac> echo 'usb:v413cp8147d*dc*dsc*dp*ic02isc0Aip00*' > /sys/module/cdc_ether/drivers/usb\:cdc_ether/new_id
[15:05] <asac> bash: echo: write error: Invalid argument
[15:07] <asac> echo "0 0 ffffffff ffffffff 413c 8147" > /sys/module/cdc_ether/drivers/usb\:cdc_ether/new_id
[15:07] <asac> amitk: that didnt complain
[15:07] <asac> ;)
[15:08] <amitk> asac: New PCI IDs may be added to a device driver pci_ids table at runtime
[15:08] <amitk> as shown below:
[15:08] <amitk> echo "vendor device subvendor subdevice class class_mask driver_data" > \
[15:08] <amitk> /sys/bus/pci/drivers/{driver}/new_id
[15:08] <amitk> All fields are passed in as hexadecimal values (no leading 0x).
[15:08] <amitk> The vendor and device fields are mandatory, the others are optional. Users
[15:08] <amitk> need pass only as many optional fields as necessary: o subvendor and subdevice fields default to PCI_ANY_ID (FFFFFFFF) o class and classmask fields default to 0 o driver_data defaults to 0UL.
[15:08] <amitk> Note that driver_data must match the value used by any of the pci_device_id
[15:08] <amitk> entries defined in the driver. This makes the driver_data field mandatory
[15:08] <amitk> if all the pci_device_id entries have a non-zero driver_data value.
[15:08] <amitk> asac: so usb should be the same
[15:10] <asac> amitk: yeah ... but it didnt really do anything 
[15:10] <asac> but i dont know what to expect
[15:10] <asac> i hoped that it showed up in hal ;
[15:11] <anubhavrocks> asac: but the string you echo'd is diffrent from what amitk said
[15:11] <asac> yaeh
[15:12] <anubhavrocks> you mean to say PCI and USB have diffrent conventions?
[15:12] <asac> echo "413c 8147" > /sys/module/cdc_ether/drivers/usb\:cdc_ether/new_id
[15:13] <asac> amitk: would you think that that triggers udev events automatically?
[15:15] <anubhavrocks> asac: i think this should work
[15:15] <amitk> asac: it should, if the driver can actually bind to that particular device
[15:16] <asac> i am quite sure it would work as its the same device just rebranded for dell
[15:16] <amitk> http://jk.ufisa.uninett.no/usb/
[15:16] <amitk> asac: ^
[15:19] <asac> hmm ... unplugging is difficult for me ;)
[15:21] <asac> ok trying udev rule
[15:25] <asac> any idea what zaurus driver does?
[15:27] <asac> ok rebooting
[15:33] <asac> no change
[15:34] <asac> not sure whz zaurus is always loaded
[15:35] <anubhavrocks> blacklist the driver if you don't want it to load
[15:36] <asac> i did that
[15:38] <anubhavrocks> your problem is that when you insert your device the zaurus module loads instead of cdc_ether?
[15:39] <asac> not sure. could be ... i think my problem is that just the device/vendor id is not enough
[15:39] <asac> wait a sec
[15:39] <asac> http://paste.ubuntu.com/144215/
[15:39] <anubhavrocks> checkk the output of lsusb and make sure you enter the correct Vid Pid 
[15:39] <asac> i think i also need to tell new_id that its USB_CDC_SUBCLASS_MDLM,
[15:40] <asac> anubhavrocks: well. those are correct ;)
[15:40] <asac> i get complain about invalid mdlm descriptors in dmesg
[15:40] <asac> so i think thats really the problem
[15:42] <asac> 16:08 < amitk> echo "vendor device subvendor subdevice class class_mask driver_data" > \
[15:42] <asac> how could i encode a subclass there?
[15:45] <anubhavrocks> asac: lsusb -v 
[15:45] <asac> so back to square oone ... how can i just build this bloody .c file ;)
[15:45] <asac> anubhavrocks: the ids are right :2)
[15:45] <asac> wait a sec
[15:45] <anubhavrocks> to get the subclass etc
[15:45] <asac> Bus 001 Device 003: ID 413c:8147 Dell Computer Corp. 
[15:45] <asac> ah
[15:45] <asac> ok
[15:46] <asac> anubhavrocks: well. the problem is that i dont kinow how to encude subclass in the echo above ;)
[15:47] <asac> anubhavrocks: http://paste.ubuntu.com/144220/
[15:49] <asac> isnt there a bloody gcc command to make a .ko out of .c ?
[15:51] <asac> ok so i guess i will go for hexedit option
[15:53] <asac>  that worked!!
[15:54]  * asac dances!!
[15:54] <asac> amitk: thanks :) ... hexeidt was the right thing i needed
[15:54] <asac> [ 1541.258987] usb0: register 'cdc_ether' at usb-0000:00:1d.7-6, CDC Ethernet Device, 02:80:37:ec:02:00
[15:55]  * asac back to modemmanager hacking ;)
=== Omegamoon|away is now known as Omegamoon
=== k-s is now known as k-s[AWAY]
[21:09] <pjwaffle> hi this is a little off topic but it is for kernel purposes... how do you create a apt repo? I need to know so I can setup a repository for testing git version of kernel
=== k-s[AWAY] is now known as k-s
=== k-s is now known as k-s[AWAY]