2.6.24-17-generic linux headers have not been made available yet, so I can't assemble the corresponding slamr. Should be available in a few days. Meanwhile please $ dmesg >> dmesg.txt and send us the dmesg.txt, to help analyze the bootup problem MarvS scanModem maintainer On Wed, May 28, 2008 at 1:54 AM, W. Ekkehard Blanz <ekkehard.blanz@xxxxxxxxx> wrote: > only partial success :-( > > I downloaded the slamr 2.6.24-16-generic as instructed and its setup went fine > and detected a modem at ttySL0 and tested it successfully. When I tested it > with efax, the fax modem made contact with another fax modem - then there > were a bunch of timeouts - they may have to do with wrong settings in efax, > however(??). Worse: after a reboot, efax couldn't connect to the modem > anymore: permission denied. Also > sudo slmodemd -c USA /dev/slamr0 > always gives me > error: mdm setup: cannot open dev `/dev/slamr0': Device or resource busy > error: cannot setup device `/dev/slamr0' > > I tried "unloading" as instructed in the boot.txt - didn't change anything - > the modem becomes inaccessible after each reboot and only the slamr setup > fixes it temporarily. > > dmesg tells me that "PCI interrupt for device 0000:02:09.0 disabled", but I > don't know what to do about it. Any good ideas before I start hacking the > grub/menu.lst with a few options (let alone randomly up- or downgrading the > kernel or even switching the distro)? > > One more thing: Ubuntu has meanwhile upgraded to 2.6.24-17-generic - I tried > all of the above booting into 2.6.24-16-generic, because slamr setup is picky > about it. But if there was a slamr for 2.6.24-17-generic available somewhere > that would not only help me with some of the kernel up and downgrading > exercises, it would also let me use the latest available kernel. > >
