IIRC that is fixed by installing the latest setserial.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen [EMAIL PROTECTED] Perth, Western Australia
voice +61 8 9316 2486 32.0125S 115.8445Evk6lj Debian Linux
Lindsay Allen writes:
IIRC that is fixed by installing the latest setserial.
Ever since I switched to the dev kernel, I've had the following
message on boot:
TIOCSER?WILD ioctl obsolete, ignored
Yup, that fixed it. Thanks!
Ever since I switched to the dev kernel, I've had the following
message on boot:
TIOCSER?WILD ioctl obsolete, ignored
I doesn't sound dangerous or anything, but a boot error just doesn't
look good. So does anyone know how I could fix this? Is it a bug, just
like the SIOCADDR thingy?
Hi,
Ever since I switched to the dev kernel, I've had the following
message on boot:
TIOCSER?WILD ioctl obsolete, ignored
I doesn't sound dangerous or anything, but a boot error just doesn't
look good. So does anyone know how I could fix this? Is it a bug, just
like the SIOCADDR
Ossama Othman writes:
Hi,
Ever since I switched to the dev kernel, I've had the following
message on boot:
TIOCSER?WILD ioctl obsolete, ignored
I doesn't sound dangerous or anything, but a boot error just doesn't
look good. So does anyone know how I could fix this? Is it a bug, just
5 matches
Mail list logo