Re: breakage of setserial in Sarge

From: W. Paul Mills (Paul-not_at_Mills-USA.com)
Date: 08/21/05

  • Next message: qee iiii: "how to change desktop manager"
    To: debian-user@lists.debian.org
    Date: Sat, 20 Aug 2005 17:12:10 -0500
    
    

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Uwe Dippel wrote:
    > setserial is broken, with respect to several aspects.
    >
    > Here is my story:
    > Internal Modem on ttyS2 (COM3), IRQ5.
    >
    > Since the Linux kernel is too dumb to find out (the BSDs always find on
    > their own, but this is another topic), I install setserial.
    > Immediately it asks and suggests 'autosave once'. Okay, done.
    > But it doesn't recognise my modem with the correct parameters.
    > So I have to issue
    > setserial /dev/ttyS2 irq 5
    > Now the modem works.
    >
    > How to save the state for after a boot ?
    > On RH I used setserial stop. Tried, doesn't work. That's okay, we are on
    > Debian.
    > man setserial says: /etc/serial.conf
    > But it doesn't exist. The archive says: dpkg-reconfigure setserial.
    > It asks me if I want to save the current state (autoconfigure once), and I
    > say 'yes'. But still, it doesn't survive the boot. It also does not
    > produce a serial.conf.
    >
    > We have to admit, that man setserial is wrong, and the function of saving
    > the configuration beyond a reboot is broken.
    >
    > Here is how to do it:
    > Install setserial, click 'autosave once'.
    > Make your modem work using setserial with all necessary options.
    > Once it works and
    > setserial -bg /dev/ttyS*
    > shows the good values,
    > apt-get remove --purge setserial
    > apt-get install setserial
    >
    > Now the reboot should be okay.
    > Reason:
    > 1. the automatic configuration at install is the only time when the file
    > is written. A dpkg-reconfigure will simply do nothing. Plus it fails
    > to warn that it will *not save anything*.
    > 2. contrary to logic and man pages, the config is saved as
    > /var/lib/setserial/autoserial.conf
    > 3. the dpkg --configure started immediately before install is logically
    > wrong: since there is no setserial before you install setserial, all
    > settings are default settings, taken from BIOS / Kernel. There is no need
    > at all to save them 'autosave once'; because any reboot will bring them back.
    > Only after one or more setserial commands will a 'save' be of any use.
    > Worse: only *after* using setserial does 'autosave once' make any sense.
    > But then it does not accept new values any longer.
    >
    > Shoddy quality control, sorry to say.
    >
    > For those not having read the full story and asking how should it work ?:
    > 1. go back to saving the configuration under /etc/
    > 2. do not 'force' an autosave at install. Rather ask:
    > "Do you want to save your settings now ? Probably you don't, because you
    > installed setserial to change the default settings, right ?
    > So you better chose No now; fix the settings for your serial ports.
    > When you are done, run dpkg-reconfigure setserial to store your settings
    > to be permanent and survive a reboot".
    > When the choice is 'Yes', the current menu comes up.
    > At the suggested 'No', the dpkg --configure setserial is exited.
    > When the settings are done,
    > dpkg-reconfigure setserial will 'autosave once' create the serial.conf in
    > /etc/
    >
    > Uwe

    Perhaps you should read "/usr/share/doc/setserial/README.Debian.gz"
    See "/usr/share/doc/setserial/serial.conf" for a sample serial.conf file
    if you need one. Also check bugs.debian.org as there are some known bugs
    which will affect SOME users.

    Paul

    - --
    /********************** Running Debian Linux ************************
    * For God so loved the world that He gave his only begotten Son, *
    * that whoever believes in Him should not perish... John 3:16 *
    ********** W. Paul Mills ********** http://Mills-USA.com/ **********/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.1 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

    iD8DBQFDB6q6u4tRirKTPYwRAmkxAJ9oQFRun+TpzKDWh0OhFPQ2FmpJvACfQNqQ
    D5t7W/+RThYZp8vFYZNe5mg=
    =mq/4
    -----END PGP SIGNATURE-----

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: qee iiii: "how to change desktop manager"

    Relevant Pages

    • breakage of setserial in Sarge
      ... Immediately it asks and suggests 'autosave once'. ... But it doesn't recognise my modem with the correct parameters. ... Now the reboot should be okay. ... settings are default settings, ...
      (Debian-User)
    • Re: Virus?
      ... >years using windows 98 SE. ... >It suddenly would only boot in safe mode for no apparent reason. ... Performed a step by step reboot and the ... Rebooted and checked the BIOS settings again ...
      (comp.sys.ibm.pc.hardware.chips)
    • Re: Update of Windows Update fails with error 0x80070005
      ... Do a reboot again. ... Then check if you can start and stop the Automatic Updates service ... What are the settings (registry ...
      (microsoft.public.windowsupdate)
    • Virus?
      ... years using windows 98 SE. ... It suddenly would only boot in safe mode for no apparent reason. ... Performed a step by step reboot and the ... Rebooted and checked the BIOS settings again ...
      (comp.sys.ibm.pc.hardware.chips)
    • Re: Server is working but unable to logon by any means
      ... I changed the registry settings back to original settings and rebooted after ... So I've rebooted the server with no changes done at all. ... Safe Mode is not working - same issue it will not display logon screen ... difference after reboot. ...
      (microsoft.public.windows.server.general)