[Bug 7207] Improving ZIP drive support
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Sat Mar 5 22:56:04 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=7207
Ubuntu | linux
------- Additional Comments From vincent.trouilliez at modulonet.fr 2005-03-05 22:56 UTC -------
> > 1) 'ppa' module not loaded
>
> This driver is only used for parallel port devices, so I don't expect that you
> had this problem with your IDE model.
Well yes, of course, the module for the IDE one was ide-floppy IIRC (fro memory)
and it didn't get loaded either.
> I don't think that parallel-attached devices can be reliably autodetected, so I
> don't think this will go away
Ah, I understand. So that's why my printer was detected properly, but not
installed, in case the detection got it wrong ?
Ah well, that's okay then. As long as the parallel device do work properly, I
guess a little bit of manual tweaking is acceptable.
> > 2) 'sda4' device not created
>> This seems to overlap/conflict with 4)
Hmmm yes, maybe ;-P
> Later, you say that this happens sometimes, but not reliably. Check
> ~/.xsession-errors in all cases.
I uploaded the file.There are loads of errors in there, not sure what to look
for. Only thing that caught my eye were errors like :
** ERROR **: file gam_tree.c: line 146 (gam_tree_remove): assertion failed:
(g_node_n_children(node->node) == 0)
aborting...
end from FAM server connection
failed to read() from server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
failed to read() from server connection
end from FAM server connection
But I am not sure if it had anything to do with my parallel ZIP drive problems ???
> So eject from the command line works reliably, but ejecting from the desktop
does not?
Yes.
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-team
mailing list