Has anyone been able to port the driver provided by Intel for the modem chipset mentioned in the subject line to the 2.6 kernel?
Regards,
On Sun, 2004-05-30 at 00:01, Cosmin Hanulescu wrote:
Has anyone been able to port the driver provided by Intel for the modem chipset mentioned in the subject line to the 2.6 kernel?
since that is a binary only kernel module that will be really hard for anyone except intel to do.
However you may be lucky if your modem is supported by the snd_intel8x0m alsa driver, that exports your modem as sound device to userspace, and a userspace app to "whistle" modem sounds into that exists.
Arjan van de Ven wrote:
since that is a binary only kernel module that will be really hard for anyone except intel to do.
Well, I thought that the binary part of the bundle Intel provides is pretty much the same, only the the code that wrap around it and does the interfacing with the kernel should be changed according to 2.6. But I must admit that I can't tell more for I lack skills in the kernel internals area.
I did compile the thing, changing here and there the headers, but, obviously, the resulting object file didn't work, as I was expecting..
However you may be lucky if your modem is supported by the snd_intel8x0m alsa driver, that exports your modem as sound device to userspace, and a userspace app to "whistle" modem sounds into that exists.
Now that's a funny thing, I'll have a look at it.
Thank you
We are in 2004 and lot and lots of people have USB keys. The fact that FC2 does not do the proper thing for detecting the insertion of an USB key, mounting it and popping a Nautilus/Konqueror window on it must be considered a bug.
Now the question is: when filling a bug treport in bugzilla in which category fill it (Nautilus/HotPlug/BlueCurve)?
On Thursday 03 June 2004 03:43 pm, Jean Francois Martinez wrote:
We are in 2004 and lot and lots of people have USB keys. The fact that FC2 does not do the proper thing for detecting the insertion of an USB key, mounting it and popping a Nautilus/Konqueror window on it must be considered a bug.
It kinda does, except not with all USB keys and without doing graceful things like adding the new device to the nautilus devices screen.
If you look in /etc/updfstab.conf.default, you will notice a lot of devices listed. Not all, but a lot. For example, for my USB key I had to add separate entries for my devices, e.g. in the diskonkey field:
match hd "Ultra Floppy"
because my USB key identifies itself as:
kernel: usb 2-1: new full speed USB device using address 15 kernel: scsi12 : SCSI emulation for USB Mass Storage devices kernel: Vendor: OTi Model: Ultra Floppy Rev: 1.11 kernel: Type: Direct-Access ANSI SCSI revision: 02 kernel: SCSI device sda: 64512 512-byte hdwr sectors (33 MB) kernel: sda: assuming Write Enabled kernel: sda: assuming drive cache: write through kernel: sda: sda1 kernel: Attached scsi removable disk sda at scsi12, channel 0, id 0, lun 0
The "Model: Ultra Floppy" part is how updfstab identifies the device and knows what to do with it. So, once the "match" for this device is added to /etc/updfstab.conf, the process becomes automatic. Once you plug in your device, you will see the device added to fstab and do the ownerships correctly to the console user.
The only problem is that nautilus will have no idea about the new device, so you can only mount it from the command line. This is an unhappy situation, but at least it's getting somewhere. I don't know if I would want the devices automatically mounted on insertion, as this could lead to unhappy places, but just making nautilus aware of changes happening to fstab would be great.
--icon
On Thu, 3 Jun 2004 00:38:29 -0400, Konstantin Ryabitsev icon@linux.duke.edu wrote:
The only problem is that nautilus will have no idea about the new device, so you can only mount it from the command line. This is an unhappy situation, but at least it's getting somewhere. I don't know if I would want the devices automatically mounted on insertion, as this could lead to unhappy places, but just making nautilus aware of changes happening to fstab would be great.
I really need to get a usb equiped fc2 system installed i guess. The right click Disk submenu in fc1 happily showed my usb keydrive, and the 3 other brands i have access to. Did the UI change to the Computer icon from the right click menu break that fstab lookup?
-jef
On Thursday 03 June 2004 04:08 pm, Jeff Spaleta wrote:
I really need to get a usb equiped fc2 system installed i guess. The right click Disk submenu in fc1 happily showed my usb keydrive, and the 3 other brands i have access to. Did the UI change to the Computer icon from the right click menu break that fstab lookup?
I think that went away in gnome-2.6. Now to see and mount your devices you have to go to "This Computer" on your desktop, which won't see the new devices. At least not in my tests, I'll gladly be proven wrong. :)
--icon
On Thu, 2004-06-03 at 15:43, Jean Francois Martinez wrote:
We are in 2004 and lot and lots of people have USB keys. The fact that FC2 does not do the proper thing for detecting the insertion of an USB key, mounting it and popping a Nautilus/Konqueror window on it must be considered a bug.
Now the question is: when filling a bug treport in bugzilla in which category fill it (Nautilus/HotPlug/BlueCurve)? -- Jean Francois Martinez jfm512@free.fr
This is currently being worked on with the udev/dbus/hal stack. Hopefully I can get the pieces in Rawhide soon.
On Sunday 30 of May 2004 00:01, Cosmin Hanulescu wrote:
Has anyone been able to port the driver provided by Intel for the modem chipset mentioned in the subject line to the 2.6 kernel?
Try slmodem from ftp://ftp.smlink.com/linux/unsupported/. It works with 2.6 kernel.
Regards,
-
Arjan van de Ven -
Arkadiusz Miskiewicz -
Cosmin Hanulescu -
Jean Francois Martinez -
Jef Spaleta -
John (J5) Palmieri -
Konstantin Ryabitsev